Re: [us...@bb.net] And even more multi-master anecdotes.

> On Aug 18, 2017, at 10:16 AM, Pierre Tardy wrote: > > So we may want to allow administrator to enforce maximal limits in the REST > API service. > This means that if people want more, they deal with paging in their scripts. > gitlab has a default policy of 100 for all

Re: [us...@bb.net] And even more multi-master anecdotes.

Since you are running buildbot at very large scale, have you ever considered running the buildbot master under pypy ( https://pypy.org/ )? I would be curious what your statistics would be in that case. -- Craig ___ users mailing list users@buildbot.net

Re: [us...@bb.net] And even more multi-master anecdotes.

Hi all, I think the API requests that Neil mentions may have been a red herring. He credits the elimination of the API requests with the reduced memory consumption, but what actually did the trick was deleting 95% of the buildrequests from the database. I've been digging into the UI

Re: [us...@bb.net] And even more multi-master anecdotes.

Hi again, This morning's update, after spending some quality time trying to figure out just what's going on... We stuffed in some of the google perftools stuff to try to see where memory was going. That didn't tell us much, other than there's a bunch of data in dictionaries (big surprise

Re: [us...@bb.net] And even more multi-master anecdotes.

Hi guys, Thanks for the update. Sounds like you are having a lot of fun.. or not. Buildbot has a Janitor since a few releases: http://docs.buildbot.net/latest/manual/cfg-configurators.html#janitorconfigurator I think it might be time for you to improve this and also cleanup beyond the log. the