Balancing Distributed Nodes

40 views
Skip to first unread message

Fabricio Leotti

unread,
Nov 23, 2015, 6:29:39 PM11/23/15
to jenkins...@googlegroups.com
Hello!

Normally I use the USAGE strategy of my nodes as "utilize this node as
much as possible" and group labels (in this case 2 nodes).

I am getting too much difference between the loads of the 2 nodes. I
was thinking if the balancing strategy would change if I keep the
labels and change the strategy to "Only build jobs with label
restriction matching this node". Should I expect to observe a
different behaviour?

Thanks in advance,

Fabricio Leotti

Daniel Beck

unread,
Nov 23, 2015, 6:39:41 PM11/23/15
to jenkins...@googlegroups.com
Maybe this helps?

https://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAEsRhy1Nd1DaVxzA_UVn9Nv7PToDQunsed96PGOCVJ1Yqfx1tQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

Rock Rockenhaus -X (crockenh - INSIGHT GLOBAL INC at Cisco)

unread,
Nov 23, 2015, 6:40:50 PM11/23/15
to jenkins...@googlegroups.com

Fabricio Leotti

unread,
Nov 24, 2015, 6:54:10 AM11/24/15
to Jenkins Users, m...@beckweb.net
Yes. Probably this helps. I was also trying to remember what was the default behaviour of Jenkins when distributing builds. Thought that I could fix something without using plugins. Thanks !

Fabricio Leotti

unread,
Nov 24, 2015, 6:54:57 AM11/24/15
to Jenkins Users
From what I read in the docs, it's more appropriate for cases where you work with multiple master, right?

Thanks for your answer!

Baptiste Mathus

unread,
Nov 24, 2015, 12:04:38 PM11/24/15
to jenkins...@googlegroups.com

Didn't double check, but IIRC the default behaviour for Jenkins us to try to make the build run of the previous as much as possible. This can drastically improve performance for some contexts (say big repo to clone, things to cache and so on).

HTH

Cheers

Fabricio Leotti

unread,
Nov 24, 2015, 12:49:28 PM11/24/15
to Jenkins Users, m...@batmat.net
You recall correctly, Baptiste. That's the exact default behaviour.

Thanks a lot!
Reply all
Reply to author
Forward
0 new messages