On Tue, Jan 20, 2015 at 12:09 PM, Torge Riedel <[email protected]> wrote:
> Hi @all, > > just got a server shutdown by my provider caused by 100% CPU load by > apache processes. > > After reactivation I played around and found the following: > > - I have TracTicketChangeLogPlugin installed (the latest version from > repo, updated on 18th January 2015) > - If I view a ticket with 3 entries in the commit history I get an apache > process with 100% CPU load, staying at this level > - Killing this process raises another one reaching 100% CPU load, staying > at this level > - Killing the second process too reduces the server load to a normal level > - After deactivation of the plugin I can view any ticket without a problem > -> seems to be related to the ticket > > Any ideas? > I'm sure that I had no problems with this plugin of an older version. > > Regards > Torge Which branch have you installed from, 0.12 or 1.0? What is the version of the plugin? I don't see anything in recent changes that looks concerning, but you could try rolling back to that earlier version of the plugin and check if the issue occurs with that one ticket. What version / revision were you running prior to updating the plugin on 18th of Jan? Can you reproduce the issue with more that one of the tickets in your system? The TracTicketChangeLogPlugin runs a LIKE query on the revision table on every request. I'm no database performance expert, but that has concerned me since I first started looking at the plugin. An outline of changes for improving the plugin can be found here: http://trac-hacks.org/ticket/11821 -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
