Reduced the number of executors to 2 on master.
I was watching how overloaded Jenkins was well it was running 3 jobs on the master server. It was so overload that the Jenkins website became unresponsive for a several min. So I reduced the number of jobs that will on the master. Thanks Robert
----- Original Message -----
From: "Robert Middleswarth" <robert@middleswarth.net> To: "Karsten 'quaid' Wade" <kwade@redhat.com>, "Eyal Edri" <eedri@redhat.com>, "Mike Burns" <mburns@redhat.com>, "infra" <infra@ovirt.org> Sent: Tuesday, July 24, 2012 10:01:13 PM Subject: Reduced the number of executors to 2 on master.
I was watching how overloaded Jenkins was well it was running 3 jobs on the master server. It was so overload that the Jenkins website became unresponsive for a several min. So I reduced the number of jobs that will on the master.
if we have enough slaves, it's best practice to set it even to 0, and not run any jobs on it.
Thanks Robert
On 07/25/2012 02:42 AM, Eyal Edri wrote:
----- Original Message -----
From: "Robert Middleswarth" <robert@middleswarth.net> To: "Karsten 'quaid' Wade" <kwade@redhat.com>, "Eyal Edri" <eedri@redhat.com>, "Mike Burns" <mburns@redhat.com>, "infra" <infra@ovirt.org> Sent: Tuesday, July 24, 2012 10:01:13 PM Subject: Reduced the number of executors to 2 on master.
I was watching how overloaded Jenkins was well it was running 3 jobs on the master server. It was so overload that the Jenkins website became unresponsive for a several min. So I reduced the number of jobs that will on the master.
if we have enough slaves, it's best practice to set it even to 0, and not run any jobs on it.
There is one Job that is set to run only on master but I don't have problem dropping down the number of jobs running on master. I will bring it down to 1 that should help lower the load on master even more. Thanks Robert
Thanks Robert
On Wed, 2012-07-25 at 09:04 -0400, Robert Middleswarth wrote:
On 07/25/2012 02:42 AM, Eyal Edri wrote:
----- Original Message -----
From: "Robert Middleswarth" <robert@middleswarth.net> To: "Karsten 'quaid' Wade" <kwade@redhat.com>, "Eyal Edri" <eedri@redhat.com>, "Mike Burns" <mburns@redhat.com>, "infra" <infra@ovirt.org> Sent: Tuesday, July 24, 2012 10:01:13 PM Subject: Reduced the number of executors to 2 on master.
I was watching how overloaded Jenkins was well it was running 3 jobs on the master server. It was so overload that the Jenkins website became unresponsive for a several min. So I reduced the number of jobs that will on the master.
if we have enough slaves, it's best practice to set it even to 0, and not run any jobs on it.
There is one Job that is set to run only on master but I don't have problem dropping down the number of jobs running on master. I will bring it down to 1 that should help lower the load on master even more.
Before bringing it down any more, can we look at what requires master to run and if we can/should move those jobs off master? Thanks Mike
Thanks Robert
Thanks Robert
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
participants (3)
-
Eyal Edri -
Mike Burns -
Robert Middleswarth