On Wed, Jun 13, 2012 at 2:58 PM, Nils Bruin <nbr...@sfu.ca> wrote: > On Jun 13, 11:35 am, William Stein <wst...@gmail.com> wrote: >> For "fun", I just did >> >> /etc/init.d/apache2 restart >> /etc/init.d/postgresql restart >> >> which might impact something... > > Has anyone checked trac's logs to see *why* trac is slow? With fully > automated things like patchbots, it wouldn't surprise me if trac is > just overloaded by runaway patchbot requests, particularly now that > there are various patchbot out in the wild.
That is a good question. In terms of patchbot's impact on trac, the server scrapes the page whenever the page is visited (as detected by serving the blurb on the trac page). This essentially doubles the load of any manual human interaction (though the database, cache, etc. should be hot for this second request). The only other impact is that the patches themselves are downloaded directly in the clients when testing a ticket. If trac can't handle serving patches as fast as we can apply, rebuild, and test them then there's something very wrong... - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
