This issue is about sourceware builder webapp software addressed by the comment [1] For example, systemtap-fedrawhide-x86_64 builds page[2] sometimes shows "Builds: None" like below rather than a list of the builds. Once I see the "Builds: None", then I cannot see a list of builds for a while. Ideally I always want to see a list of builds. [1] https://sourceware.org/bugzilla/show_bug.cgi?id=32497#c3 [2] https://builder.sourceware.org/buildbot/#/builders/200
Perhaps, is this issue related to a number of the builds shown on the builds page? For example, the above page [2] shows the latest 200 builds. Can we change the number of builds printed initially into a smaller number such as 100 or 50?
Yeah that is slightly odd. As far as I can tell it happens when the buildbot is "too busy". Which seems to be when there are 15+ builds running at the same time. At least when there less than 15 builds running everything seems snappy and the list of builds appears almost instantly, once it is more than 15 builds the list of builds simply doesn't appear.
(In reply to Mark Wielaard from comment #2) > Yeah that is slightly odd. As far as I can tell it happens when the buildbot > is "too busy". Which seems to be when there are 15+ builds running at the > same time. At least when there less than 15 builds running everything seems > snappy and the list of builds appears almost instantly, once it is more than > 15 builds the list of builds simply doesn't appear. Hi Mark, Thanks for your explanation. I got 2 ideas: 1. The sourceware builder system can implement a queuing system receiving a request, triggering buildbot's task, and managing the number of maximum running builds. I just found the following article. I am not sure about the details. https://blog.containerize.com/top-5-open-source-message-queue-software-in-2021/ 2. Are the buildbot and webapp are running in the same server? Perhaps, you can separate a server running builtbot from a server running webapp. In this case, the buildbot executed in a server is to upload the result data into another server where webapp is running.
Did a bit of homework on buildbot query delays. https://docs.sqlalchemy.org/en/14/dialects/sqlite.html#database-locking-behavior-concurrency sqlalchemy (buildbot's ORM layer) may be lumping SQL write operations together with pure queries, making the latter slow when there is a lot of write traffic to the database (such as when slaves are producing ample output).