Re: Jenkins slowness

2019-02-08 Thread Ismaël Mejía
/beam_PreCommit_Java_Cron/914/ and looking >>>> into cacheable task there seems to be lots of work done now which >>>> previously was cacheable. >>>> >>>> Not sure, whether this is the culprit- or part of it -, but I d suggest to >>>> upg

Re: Jenkins slowness

2019-02-07 Thread Michael Luckey
gradle 5 pretty fast. > > On Thu, Feb 7, 2019 at 8:18 PM Udi Meiri <mailto:eh...@google.com>> wrote: > If anyone has done any investigation/is working on this please share. > > I'm investigating Jenkins slowness. I've noticed it happening since > yesterday: precommits

Re: Jenkins slowness

2019-02-07 Thread Yifan Zou
t;>>> previously was cacheable. >>>> >>>> Not sure, whether this is the culprit- or part of it -, but I d suggest >>>> to upgrade to gradle 5 pretty fast. >>>> >>>> On Thu, Feb 7, 2019 at 8:18 PM Udi Meiri wrote: >>>>

Re: Jenkins slowness

2019-02-07 Thread Udi Meiri
ems to be lots of work done now which >> previously was cacheable. >> >> Not sure, whether this is the culprit- or part of it -, but I d suggest >> to upgrade to gradle 5 pretty fast. >> >> On Thu, Feb 7, 2019 at 8:18 PM Udi Meiri wrote: >> >>> If anyone

Re: Jenkins slowness

2019-02-07 Thread Udi Meiri
gt;>> >>> Not sure, whether this is the culprit- or part of it -, but I d suggest >>> to upgrade to gradle 5 pretty fast. >>> >>> On Thu, Feb 7, 2019 at 8:18 PM Udi Meiri wrote: >>> >>>> If anyone has done any investigation/is working on thi

Re: Jenkins slowness

2019-02-07 Thread Chamikara Jayalath
ch > previously was cacheable. > > Not sure, whether this is the culprit- or part of it -, but I d suggest to > upgrade to gradle 5 pretty fast. > > On Thu, Feb 7, 2019 at 8:18 PM Udi Meiri wrote: > >> If anyone has done any investigation/is working on this please share. >

Re: Jenkins slowness

2019-02-07 Thread Michael Luckey
which previously was cacheable. Not sure, whether this is the culprit- or part of it -, but I d suggest to upgrade to gradle 5 pretty fast. On Thu, Feb 7, 2019 at 8:18 PM Udi Meiri wrote: > If anyone has done any investigation/is working on this please share. > > I'm investigatin

Jenkins slowness

2019-02-07 Thread Udi Meiri
If anyone has done any investigation/is working on this please share. I'm investigating Jenkins slowness. I've noticed it happening since yesterday: precommits taking 3 hours to start, phrase commands similarly taking as much time to register. My current theory is that we have a job that's

Re: Jenkins slowness

2019-02-07 Thread Udi Meiri
> I'm investigating Jenkins slowness. I've noticed it happening since > yesterday: precommits taking 3 hours to start, phrase commands similarly > taking as much time to register. > > My current theory is that we have a job that's are taking much longer than > usual to run. >

Re: Jenkins slowness

2018-03-09 Thread Lukasz Cwik
The only statistics I get to see are the build load statistics: https://builds.apache.org/computer/beam1/load-statistics On Fri, Mar 9, 2018 at 10:43 AM, Udi Meiri wrote: > Is there a way to see OS load statistics? > > On Fri, Mar 9, 2018 at 10:24 AM Jason Kuster

Re: Jenkins slowness

2018-03-09 Thread Udi Meiri
Is there a way to see OS load statistics? On Fri, Mar 9, 2018 at 10:24 AM Jason Kuster wrote: > Jenkins executors are probably less beefy than your development machine > and also have two slots, thus are likely running two builds at once, > causing extra slowness. > > >

Re: Jenkins slowness

2018-03-09 Thread Jason Kuster
Jenkins executors are probably less beefy than your development machine and also have two slots, thus are likely running two builds at once, causing extra slowness. On Fri, Mar 9, 2018 at 10:18 AM Udi Meiri wrote: > Hi, > > Does anybody know why Jenkins hosts take so long to

Jenkins slowness

2018-03-09 Thread Udi Meiri
Hi, Does anybody know why Jenkins hosts take so long to run? For example, beam1 was running beam_PostCommit_Python_Verify and I saw this time for running "tox -e py27": Ran 1535 tests in 403.860s on my workstation I got: Ran 1535 tests in 160.242s Is there any way to troubleshoot this? Each