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
