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 16348 - Expanding of folder with java files too slow!
Summary: Expanding of folder with java files too slow!
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: Sun All
: P1 blocker (vote)
Assignee: Svata Dedic
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2001-10-08 15:51 UTC by Jan Zajicek
Modified: 2007-09-26 09:14 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Jan Zajicek 2001-10-08 15:51:33 UTC 
dev #20011008

Start ide, mount openide.src package as localfilesystem, now browse through the
package. This is regression. For more info, check issue #14222.

I consider this as P1, because of bad impact at users. I recommend to include
this fix into beta.
Comment 1 Petr Nejedly 2001-10-08 15:57:59 UTC 
Adding PERFORMANCE keyword
Comment 2 Petr Nejedly 2001-10-08 17:57:04 UTC 
The problem is particulary with Java files which causes call
to secondaryEntries in JDO constructor.

Moreover, it takes that long that it even interferes with
Java parsing thread which causes other recognitions to be started
in the mean time.
Comment 3 Svata Dedic 2001-10-09 07:49:51 UTC 
Moving to java module.
Comment 4 Svata Dedic 2001-10-09 17:40:38 UTC 
Checking code removed -- it is hooked on PROP_FILES on the DataObject.
Some performance issues remain, however: PROP_FILES is fired once for
each secondary file recognized as a part of the object. Since there is
some logic associated with the event handling, firing it several times
for one compiled java file with a bunch of inner classes.
Also, I had to override files() to keep behaviour required for
JarPackager to work when the compiler outputs classes to a different
filesystem. Standard DataNode will call this method when it goes to
compute the displayName - don't know whether it will trigger another
re-recognition or not.
Comment 5 Petr Nejedly 2001-10-10 09:18:12 UTC 
See issue #16396.
Comment 6 Jan Becicka 2001-10-19 12:26:32 UTC 
[200110190100] Verified
Comment 7 Quality Engineering 2003-07-01 13:18:11 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.