This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Search History extremely slow retrieving revision history | ||
---|---|---|---|
Product: | versioncontrol | Reporter: | bobw <bobw> |
Component: | Subversion | Assignee: | issues@versioncontrol <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | Macintosh (x86) | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Profile report - opened Search History window and clicked the Search button to bring up the full list of revisions |
Description
bobw
2009-10-28 17:12:25 UTC
*** Issue 175607 has been marked as a duplicate of this issue. *** Created attachment 90180 [details]
Profile report - opened Search History window and clicked the Search button to bring up the full list of revisions
there is some pre-processing before the actual svn log command is called. the strange thing is, that it takes so long in your case. how big is your project in files and folders? does it always take so long? any chance you could give it a try with a newer svn client? thanks fixed changeset : 151309:71f3c58f1100 author : Tomas Stupka <tstupka@netbeans.org> date : Fri Oct 30 14:31:56 CET 2009 Some quick responses: - The project I got those numbers with contains 45045 folders and 26454 files. - The svn client I'm using is the one that's already pretty new... version 1.6.2. And as I mentioned, pulling a verbose log from the command line is nearly instant. - No, it doesn't always take so long. In my testing, I noticed that sometimes it popped up relatively quickly. However, I suspect this is due to some local caching, and whatever the cache algorithm is, I don't remember previously benefitting from it in my normal work habits. - I'm not a Java programmer, but IIRC from my glance at the profile, it looked like the delays were coming from some socket code, which had me wondering if NB's means of communicating with the svn client has issues. - I see you've changed this to RESOLVED/FIXED and have a commit to go with it. That's wonderful (thanks!), but I'm curious... any comments on what was wrong? > No, it doesn't always take so long. In my testing, I noticed that sometimes it popped up relatively quickly. However, > I suspect this is due to some local caching was my guess, and yes caching might influence the response time in different scenarios > any comments on what was wrong? local files are scanned for some data which have to be merged with the returned log info and the way it was done was quite suboptimal thanks Integrated into 'main-golden', will be available in build *200911030222* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/71f3c58f1100 User: Tomas Stupka <tstupka@netbeans.org> Log: #175608 - Search History extremely slow retrieving revision history |