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 132706 - expanding "source packages" node is painfully slow
Summary: expanding "source packages" node is painfully slow
Status: RESOLVED DUPLICATE of bug 132835
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Mercurial (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@versioncontrol
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2008-04-13 16:41 UTC by hlavki
Modified: 2008-05-13 14:13 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
most of time is in this stack (3.41 KB, text/plain)
2008-04-14 17:16 UTC, hlavki 		Details
profiler screenshot (174.03 KB, image/png)
2008-04-14 17:17 UTC, hlavki 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description hlavki 2008-04-13 16:41:13 UTC 
I am using 6.1rc1 and mevenide 3.0.12 and expanding source packages is very slow. I tested it in general java project
and it works good.
Comment 1 Milos Kleint 2008-04-14 07:59:01 UTC 
did you test on comparable project size? at the time when no other background threads in the IDE were running?
It would be interesting to get a few thread dumps during the process of expanding the packages..
Comment 2 hlavki 2008-04-14 08:49:06 UTC 
yes, I created same project as netbeans java project and it works ok. I discovered that expanding source packages in 
maven project is slow only sometimes. It takes up to 20 seconds with 193 java files and 60 folders. I don't know when 
it happends.
Comment 3 Milos Kleint 2008-04-14 14:03:47 UTC 
well, this sort of thing is very hard to reliably reproduce as they are many things in play. the expanding action needs
to iterate and examine deep folder structures. ON the OS level it's speed often relies on having the stuff cached. I've
seen the same thing with "Open project" action for netbeans.org projects. There's 800+ projects in one directory but the
opening involves looking the in subdirectories as well, for nbproject/project.xml file presence. When done the first
time after computer reboot, it takes a significant amount of time, any subsequent opening (even from other IDE instance
I think) takes less time already..

A bunch of thread dumps during the 20 seconds of opening the packages would help for sure. We might indeed be doing
something wrong there. Or some other unrelated activity is happening in the IDE that eats CPU/Disk resources.
Comment 4 hlavki 2008-04-14 17:14:53 UTC 
It looks like problem with mercurial. I do some profiling and thread dumps. Results are in attachements. Problematic 
is HgUtils.isIgnored() method. I am using mercurial 1.0. May I change Component and Subcomponent of this issue to 
mercurial/code?
Comment 5 hlavki 2008-04-14 17:16:50 UTC 
Created attachment 60144 [details]
most of time is in this stack
Comment 6 hlavki 2008-04-14 17:17:29 UTC 
Created attachment 60145 [details]
profiler screenshot
Comment 7 Milos Kleint 2008-04-15 08:22:31 UTC 
reassigning to mercurial support for evaluation.
Comment 8 Padraig Obriain 2008-05-13 14:13:57 UTC 
I am closing this as a duplicate of 132835.

132835 is clsoed as a duplciate of 134902 as the attachment of that bug should fix this problem. 

*** This issue has been marked as a duplicate of 132835 ***