|
|
|
[
Permlink
| « Hide
]
TQ Berg - 16/Jan/09 11:01 PM
We are up to 70+ projects and it now takes 5 - 10 seconds for the UI to render. If we move forward we will have many more than 70 projects, so this will become critical for us soon. For our regular users, this won't be an issue, as they will only see a few projects, but for leads and project admins, it will be an issue. FWIW, incredibly slow UI rendering is one area that is driving us away from TeamCity. The many projects thing is also why it's inconvenient to maintain a separate Perforce client for each project.
We are noticing some fairly significant slowness today. I am not sure if it's UI or back-end, or some combination. One thing to note is that we have 80 some projects in Pulse today. We have 250+ more projects to add. Have you set up any tests with many projects?
Hi TQ,
Our normal acceptance test suite accumulates projects (somewhere between 100-150, in hierarchies about 3-4 levels deep) as it runs, so when there is a scalability issue our suite slows significantly and we crack out the profiler. Ideally, however, we would have a larger, more specialised test with even more projects. Any ETA on this one?
We have users complaining about the UI becoming cumbersome to handle and would really like to see the default working of the UI to have the builds collapsed. Or atleast to have it as a configurable preference in their profile. Hi Venkat,
Thanks for your input. We don't have a firm date for this change as investigation have shown it to require a significant rewrite of the UI for the dashboard/browse view changes. It should, however, be started in the next couple of weeks as we are still aiming to have it done against 2.0 and thus prior to our upcoming 2.1 beta release. |
|||||||||||||||||||||||||||||||||||||||||||||||||||