hi David,
so is 2 machines every 10 min a good rate to start from ?
regards,
On 08/08/16 16:08, David Moreau Simard wrote:
Using the new slaves has a couple objectives:
- Test the new OpenStack cloud
- Increase redundancy (given the instability of our existing slave
the past few weeks) 3) Increase concurrency/capacity
We had 16 threads on a single slave before (down from 24) and that single slave was struggling to cope when all those 16 threads were actually busy. The new slaves have 8 threads each and we lowered the amount of threads on the original slave back to 10 so it isn't loaded (and isn't crashing) as much.
So we're now at 34 threads total and I can indeed tell from our consumption logging that the usage has increased and peaks higher than before. We'll scale down the threads to 24 total, can you tell us if you see improvements ?
We're also waiting for the feature in Duffy that'll enable us to track which node is associated with which job so we can hunt jobs that are potentially not being very good citizens.
David Moreau Simard Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Mon, Aug 8, 2016 at 9:30 AM, Karanbir Singh mail-lists@karan.org wrote:
hi guys,
with an increase in the number of slaves, we've noticed that the rdo jobs are deploying machines at a much higher velocity than before - as a result the ready pool is consistently hitting the low water mark.
Rather than do an overall quota limit, I'm looking at limiting the number of duffy deploy's per 10 min cycle, but rather than propose something I'd like to see what folks think is a reasonable number to start from ?
regards,
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users