This project is read-only.
1

Closed

Issue Log taking time to load

description

Hi,

I am using a plug-in for Issue Tracker to integrate with TFS. I have noticed that the Issue Log page is taking more than 10 minutes to load.

When I enabled the debugging I can see the command
command:FindMentionsByChangeset is taking more than .5 seconds to return. Is that expected?

I can also see number of times FindMentionsByChangeset is called. Is there a way to limit on number of changesets being queried?

Thanks,
Ramesh K.
Closed Nov 22, 2013 at 10:16 PM by simone_b

comments

simone_b wrote Nov 18, 2013 at 6:12 PM

I'm afraid the plugin can only go as fast as your TFS server. The command FindMentionsByChangeset queries TFS using a changeset number and retrieves the work items associated to that changeset. If it's taking that long it most likely means that TFS is taking that long to retrieve the work items for a changeset, and you should be able to reproduce the same slow behavior if you do it from within Visual Studio.

As for limiting the number of times FindMentionsByChangeset is called, there is a cache in place so that once you retrieve them once then the following times it should be much faster, and this should also persist across server restarts because the cache is on the file system. Nonetheless, it will be called at least once for each changeset, and the plugin does not have control about which and how many changesets the server will call it with.

Do you experience this slowness every time or only upon the first load of the issue log page?

Ramesh_Ka wrote Nov 22, 2013 at 1:59 PM

Thanks. yes for the first time.

simone_b wrote Nov 22, 2013 at 10:16 PM

I have added a How it works section in the homepage to explain how the plugin works so that it makes a little more sense why it can't possibly be fast as when integrating with another VCS/issue tracker.