We have 6000 trac spaces running on our main tools server at http://www.assembla.com and tools.assembla.com . Sometimes there are hundreds of users at one time. Usually, there are no performance problems.
I have been surprised at how much trac can be served from one machine. However, we do run into situations where trac consumes all of our processor and memory resources. We have found that this happens when trac renders diffs for very large files. See the notes here: http://tools.assembla.com/breakout/ticket/1413 http://trac.edgewall.org/ticket/5170 What operations are slow for you? Maybe the MySQL database is causing the problem. We use Sqlite for the trac databases. On Aug 18, 11:17 pm, Sam Minnee <[EMAIL PROTECTED]> wrote: > Hi everyone, > > We run a trac set-up where we have around 50 different projects set up > using separate environments. We've used a modified version of TraM to > provide cross-project reporting. > > While it's functional, it's incredibly slow. This might not be all > that surprising, but it's a big problem for us. > > Has anyone else had success in setting up trac with a large number of > separate projects? Does anyone have suggestions for how we might > improve performance? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. 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/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
