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 66403 - Expensive firing of changes on startup
Summary: Expensive firing of changes on startup
Status: RESOLVED FIXED
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: CVS (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@versioncontrol
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2005-10-10 16:35 UTC by _ rkubacki
Modified: 2007-01-04 17:14 UTC (History)
1 user (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 _ rkubacki 2005-10-10 16:35:23 UTC 
FileStatusProvider.refreshModifiedFiles() is called during startup to fire
FileStatusChange events for all modified files and their parents.

When this is done in my case for 160 files ~1500 conversions from File to FO are
performed while iterating throuh parents of each file. These conversions are not
for free and apparently some of them are done more than once although we can
eliminate these calls (>2/3 I guess).

BTW: why these changes are fired - did anyone get the status and attached the
listener already? I see a lot of files that should not be touched by any other
part of IDE to be processed here.
Comment 1 Maros Sandor 2005-10-18 15:43:31 UTC 
I tried to minimize event firing.

/shared/data/ccvs/repository/javacvs/cvsmodule/src/org/netbeans/modules/versioning/system/cvss/FileStatusCache.java,v
 <--  FileStatusCache.java
new revision: 1.29; previous revision: 1.28
/shared/data/ccvs/repository/javacvs/cvsmodule/src/org/netbeans/modules/versioning/system/cvss/FileInformation.java,v
 <--  FileInformation.java
new revision: 1.12; previous revision: 1.11