Skip to contentSkip to conversation

schedulers.py: run performance builds only 2x a day, not 4x

PATCH In review Alexander Kanavin 2 participants 4 messages Nov 8, 2020

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 schedulers.py: run performance builds only 2x a day, not 4x

The same builds are included in a-full, so they tend to get queued up and cause delays in builds completion, as there's only a single worker allocated to them. Let's run them less frequently to mitigate the delays.

---
 schedulers.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
schedulers.py +3 -3
index 2e8f3d5..ca63c9f 100644
@@ -306,11 +306,11 @@ schedulers.append(sched.Nightly(name='nightly-quick', branch='master', propertie
 schedulers.append(sched.Nightly(name='nightly-full', branch='master', properties=parent_default_props('a-full'),
                   builderNames=['a-full'], hour=1, minute=0, dayOfWeek=6))
 
-# Run the build performance tests at 3am, 9am, 3pm and 9pm
+# Run the build performance tests at 3am and 3pm
 schedulers.append(sched.Nightly(name='nightly-buildperf-ubuntu1604', branch='master', properties=parent_default_props('buildperf-ubuntu1604'),
-                  builderNames=['buildperf-ubuntu1604'], hour=[3,9,15,21], minute=0))
+                  builderNames=['buildperf-ubuntu1604'], hour=[3,15], minute=0))
 schedulers.append(sched.Nightly(name='nightly-buildperf-centos7', branch='master', properties=parent_default_props('buildperf-centos7'),
-                  builderNames=['buildperf-centos7'], hour=[3,9,15,21], minute=0))
+                  builderNames=['buildperf-centos7'], hour=[3,15], minute=0))
 
 # Run the AUH on the 15th of every month
 schedulers.append(sched.Nightly(name='nightly-auh', branch='master', properties=parent_default_props('auh'),
Signature · 1 line
2.29.1
#1 lore raw
Quoted 15 lines · Alexander Kanavin

The same builds are included in a-full, so they tend to get queued up and cause delays in builds completion, as there's only a single worker allocated to them. Let's run them less frequently to mitigate the delays.

---
 schedulers.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
schedulers.py +0 -0
index 2e8f3d5..ca63c9f 100644
@@ -306,11 +306,11 @@ schedulers.append(sched.Nightly(name='nightly-quick', branch='master', propertie
 schedulers.append(sched.Nightly(name='nightly-full', branch='master', properties=parent_default_props('a-full'),

schedulers.py schedulers.append(sched.Nightly(name='nightly-quick', branch='master', propertie · line 313

Quoted 10 lines
schedulers.py +3 -3
                   builderNames=['a-full'], hour=1, minute=0, dayOfWeek=6))
 
-# Run the build performance tests at 3am, 9am, 3pm and 9pm
+# Run the build performance tests at 3am and 3pm
 schedulers.append(sched.Nightly(name='nightly-buildperf-ubuntu1604', branch='master', properties=parent_default_props('buildperf-ubuntu1604'),
-                  builderNames=['buildperf-ubuntu1604'], hour=[3,9,15,21], minute=0))
+                  builderNames=['buildperf-ubuntu1604'], hour=[3,15], minute=0))
 schedulers.append(sched.Nightly(name='nightly-buildperf-centos7', branch='master', properties=parent_default_props('buildperf-centos7'),
-                  builderNames=['buildperf-centos7'], hour=[3,9,15,21], minute=0))
+                  builderNames=['buildperf-centos7'], hour=[3,15], minute=0))

I've been wondering about this but I suspect we should drop them from a-full instead...

Cheers,

Richard

#2 lore raw
Quoted 4 lines · Richard Purdie

I've been wondering about this but I suspect we should drop them from a-full instead...

Sure, I sent a patch for that.

Alex

#3 lore raw
Quoted 7 lines · Alexander Kanavin
Quoted 3 lines · Richard Purdie

I've been wondering about this but I suspect we should drop them from
a-full instead...

Sure, I sent a patch for that.

I've been thinking about this and the reason I've not done this is release builds. I'm wondering if we we can somehow make the trigger release build specific.

I think is is possible to do this, I've pushed in a patch to attempt it since I'm the one asking for the complication :)

I've tried to reconfig the controller but we'll see whether it works out or needs a full restart (when no builds are running).

Cheers,

Richard