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.

Bug 175608 - Search History extremely slow retrieving revision history
Summary: Search History extremely slow retrieving revision history
Status: RESOLVED FIXED
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Subversion (show other bugs)
Version: 6.x
Hardware: Macintosh (x86) Mac OS X
: P1 blocker (vote)
Assignee: issues@versioncontrol
URL:
Keywords:
: 175607 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-28 17:12 UTC by bobw
Modified: 2009-11-03 10:23 UTC (History)
0 users

See Also:
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 (37.26 KB, application/octet-stream)
2009-10-28 17:15 UTC, bobw
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bobw 2009-10-28 17:12:25 UTC
I'm running NB on OS X and using SVN for version control. My problem is that I'm finding the Search History window to be incredibly slow, so much so 
that I almost always avoid it in favor of using another tool. Specifically, it's slow when working with the repository; once it has the information, doing 
things like diffs and reverts work as quickly as expected. Here's an example: 

1. Open the Search History window for the project root, which corresponds with the repo root. 

2. Leave all the search fields empty and click the Search button. 

The output that results is identical to what you get with the "svn log -v" option run at the root level of the same project folder but from the command 
line. The difference is that in the test I just ran, NB took 2:30 to produce the output, while the command line (using an svn+ssh URL, *not* a working 
copy) produced it so fast that I couldn't start the timer (<1s) 

Things don't noticeably change when I specify search options, even putting a single revision number in the From and To fields (so that NB need only pull 
up one revision). Also, my teammates are seeing the same problem on their comparable systems.

My checked-out project is in the local file system, the repo is on a remote Linux server, and I'm using the svn+ssh protocol to get to it. Local svn client 
version is 1.6.2; server version is 1.4.2 (yeah, I know...). For my test project, the repo has 501 revisions and "svn log -v" on the command line produces 
19757 lines of output. I didn't time it, but I just got similar performance on a new repo with just 5 revisions and about 11k files that produces about 18k 
lines of output.

Version data:

Product Version: NetBeans IDE 6.7.1 (Build 200907230233)
Java: 1.6.0_15; Java HotSpot(TM) 64-Bit Server VM 14.1-b02-90
System: Mac OS X version 10.6.1 running on x86_64; MacRoman; en_US (nb)
Userdir: /Users/bob/.netbeans/6.7
Comment 1 bobw 2009-10-28 17:13:13 UTC
*** Issue 175607 has been marked as a duplicate of this issue. ***
Comment 2 bobw 2009-10-28 17:15:08 UTC
Created attachment 90180 [details]
Profile report - opened Search History window and clicked the Search button to bring up the full list of revisions
Comment 3 Tomas Stupka 2009-10-29 21:12:10 UTC
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

Comment 4 Tomas Stupka 2009-10-30 14:33:47 UTC
fixed

changeset   : 151309:71f3c58f1100
author      : Tomas Stupka <tstupka@netbeans.org>
date        : Fri Oct 30 14:31:56 CET 2009
Comment 5 bobw 2009-10-30 18:47:45 UTC
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?
Comment 6 Tomas Stupka 2009-10-30 19:21:06 UTC
> 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


Comment 7 Quality Engineering 2009-11-03 10:23:52 UTC
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