I've also experienced a sharp increase in CPU usage. Was testing on Amazon EC2 and even with a new environment with a couple of tickets, agilo was unusable on a Small (default) EC2 instance.
Seems to work fine using a High-CPU Medium Instance 1.7 GB of memory, 5 EC2 Compute Units (2 virtual cores with 2.5 EC2 Compute Units each), 350 GB of instance storage, 32-bit platform. Cheers .M. On Jun 27, 12:05 am, trickie <[email protected]> wrote: > Hi, > > We are evaluating the Agilo plugin for Trac, and when I enable the > plugin on a project with quite a bit of existing content (7000+ > tickets, 20M of wiki content etc) the apache processes that deal with > requests to that project exhibit very high cpu usage (almost using a > whole cpu). Pages are very slow to load (15+ secs). > > On the same server we have quite a few other Trac projects and plugins > etc. We have no issues with those projects, or this one as long as the > Agilo plugin is disabled. I am aware of some outstanding issues in > Trac 0.11 (http://trac.edgewall.org/ticket/7490for example), but we > have no issues until the Agilo plugin is enabled. We have one other > instance with the plugin enabled, but it has hardly any content, and > it seems to perform ok. > > A pie-in-the-sky question before I start setting up a debug > environment to try and re-produce the issue... is this a known issue > or related to any known issues? > > Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
