Sebastian, I have no direct experience with scaling Tracks, but I'd be surprised if you ran into major issues as long as you run in production behind a correctly configured apache / passenger, have the caching working and the DB tuned and on a sufficiently fast disk. In your use case, are the users truly concurrently working with Tracks (like if you were teaching a GTD class), or are they actually doing tasks between playing with Tracks? In the latter case I wouldn't worry at all. Either way, I would expect the configuration of the infrastructure to matter somewhat more than the app and tune them first.
Please do let us know how you make out. Best Christian On Mon, Nov 21, 2011 at 6:09 PM, Sebastian Fischmeister < [email protected]> wrote: > Hi, > > Does anyone have experience with whether Tracks scales to about 180 > concurrent users? I know that tracks starts getting unbearably slow as > the front page hits 500+ active todos, but I guess that is mostly the > view and not the database. The question is what happens when about 60 > users access a small number of todos. > > Ticket #542 is relevant for this. > > It would be cool, if someone who's more into ruby and rails were to > add ruby-prof [1] support in tracks. > > Sebastian > > [1] http://ruby-prof.rubyforge.org/ > _______________________________________________ > Tracks-discuss mailing list > [email protected] > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss >
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
