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 89039 - Deleting large number of property nodes is very slow
Summary: Deleting large number of property nodes is very slow
Status: NEW
Alias: None
Product: utilities
Classification: Unclassified
Component: Properties (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Peska
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2006-11-09 15:40 UTC by Jana Maleckova
Modified: 2011-10-21 13:58 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jana Maleckova 2006-11-09 15:40:12 UTC
NetBeans IDE Dev (Build 200611081900)
1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b99
Windows XP version 5.1 running on x86
cs_CZ (nb); Cp1250
Dual Core

Description:
============
have property with bigger amount of nodes, in my case I had 3 property files
with 1000, 2000 and 3000 nodes. I selected all nodes from one property in
project win and did delete. Results are:
deleting of 1000 nodes at once span for 31 s
deleting of 2000 nodes  - || -          2:10 min (130 s)
deleting of 3000 nodes  - || -          6:05 min (365 s)

time increases faster than I expected and in my opinion, there must be some fail.

Also there is problem if you select all nodes by keeping key shift with arrow
(down or up). After the 400th node, selecting starts to stuck. Processor is in
hight progress and selecting becomes slower and slower. I tested it on selecting
of 5000 nodes.
Comment 1 Marian Petras 2007-01-17 16:47:45 UTC
Confirmed, accepted.

It takes a lot of time, indeed. My results are:

    1000 nodes - 0:32
    2000 nodes - 1:53
    3000 nodes - 3:58

It also consumes a lot of memory.

I guess the problem is that the entries are deleted one-by-one.
Comment 2 Jan Peska 2011-10-21 13:58:30 UTC
I agree, there a performance issue but it seems like a corner case to me. Possible solution would be to implement action which deletes all selected KeyNodes at once because now every single node have to access related .properties file in sync block. -> ENHANCEMENT