I'd like to provide a bit more context.Right after restarting the master and kicking off 10 builds CPU was at 110-120%. This made the UI unusable and basically all the services were stuck, including the REST API. After 3-4 minutes like this and WITH all the 10 builds still running the CPU usage went down to 5%, stayed there for 5 minutes and all was smooth and quick again. From then on it keps oscillating, I've seen spikes of 240% :(
On Tue, Aug 2, 2016 at 4:12 PM, Francesco Di Mizio < [email protected]> wrote: > Sometimes it goes up to 140%. I was not able to relate this with a > particular builds condition - seems like it can happen any time and is not > related to how many builds are going on. > > I usually realize the server got into this state because the web UI gets > stuck. As soon as the CPU% goes back to normal values (2-3% most times) the > web finishes loading just instantly. > > Any pointers as to what might be causing this? Only reason I can think of > is too many people trying to access the web UI simultaniously - may I be > right? > >
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
