Serious server performance degredation with version 3.10.

Edit Subject

How many users access Urban Turtle in your environment?

I have tracked down the source of the problem. It is essentially the same issue that bit us when we upgrade to 3.8. The new task board area and iteration settings default to the root area and iteration. Consequently, when users accessed the task board for the first time under v3.10 they were loading in all work items (which currently amount to ~35K). This was putting a tremendous load on the system. As a work around for now, we are going to go through all of the user settings files and create default area/iteration ids for the task board. This doesn't help new users though.

I see two possible solutions: 1) the proposal I gave before that one of the config files has a setting in it to not pull more than X items back on a planning board or task board load, or 2) have a default area/id setting in the config file that is used instead of root area/root id.

Thanks John for investigating this issue on your side. We'll discuss the issue and see what solution would be the most appropriate.

Interestingly, we have implemented a way to override the root iteration/area for the Team functionality, so I would expect your second solution to be rather easy to implement.

Just an update...our workaround of setting a default iteration/area in the settings file avoid the large # of items issue and there were no complaints this morning and I didn't get yelled at by IT for bogging down the server. The sooner you can implement a fix directly in Urban Turtle the better.

Thanks John. I'll post an update as soon as I have more information regarding the status of this request.

I still think a max item count (instead of or in addition to the default area/iteration) would be useful and a good safeguard. I mean, how many people need to really pull back more than a couple hundered of items?

Thanks again. This is something we are considering for the next release.

I would like to request an urgent fix for this at least using the default area/iteration id. Even with our work around we can't keep up with the problems this issue causes. New users have the problem, and since Urban Turtle caches the setting file we are having to continually restart IIS to flush the cache. Even then, we have some users where modifying the settings file doesn't work for some reason.

I'll discuss your request with the team and see what we can do.

I installed this several days ago and seems to have alleviated the problem. Thanks for your help!

Thank you for the feedback. Keep it coming!