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 85996 - performance problem occurs after nesting elements to package using nested link from palette
Summary: performance problem occurs after nesting elements to package using nested lin...
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: General Diagram (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: _ jyothivasa
URL:
Keywords: PERFORMANCE, REGRESSION
Depends on:
Blocks:
 
Reported: 2006-09-28 07:44 UTC by Peter Lam
Modified: 2006-10-04 13:46 UTC (History)
0 users

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 Peter Lam 2006-09-28 07:44:01 UTC 
performance regression using the latest uml build 060927. only tried on windows
xp so far.

repro steps:
- create a uml project
- create a class diagram, component diagram or other type of diagram
- create and name some class elements in the diagram
- create and name a package element in the diagram
- using the Nested Link from the palette to create nested link between the class
elements and the package element
Result: the tool starts to respond very slowly
Comment 1 Sergey Petrov 2006-09-28 09:49:32 UTC 
Do you have navigator opened?
It seems the issue is in overview window, I got similar behaviour for addition
of roles to collaboration, drawing Dependancies between several classes or
drawing about 15 classes etc, the worst thing is closing of navigator do not
remove poor perfomance, user have to restart ide to get good perfomance back
even link addition actions start to work good after restart, it seems perfomance
regression appears after "global" redraw of overviw caused by addition of new
classes (objects).
Comment 2 Andrew Korostelev 2006-09-28 12:33:25 UTC 
As far as I understand from description, Petersl uses default configuration -
with opened Overview, embedded into Navigator window.
This problem is caused by overview window refreshing issue.

The problem is also reproducible under Unix systems.
With remore desctop it becomes absolutely impossible to use diagram editor
(related issue 78505).
Comment 3 Andrew Korostelev 2006-09-28 12:38:12 UTC 
related issue 86026 - Overview window closing doesn't solve the performance problem
Comment 4 Andrew Korostelev 2006-09-28 13:47:51 UTC 
see also issue 86044
Comment 5 Andrew Korostelev 2006-09-28 14:17:24 UTC 
Note, that this performance problem is highly visible because of default NB
memory settings.
See also issue 86049.
Comment 6 _ jyothivasa 2006-10-02 21:46:13 UTC 
Fixed DiagramTopComponent.java, DiagramNavigator.java, and
DiagramNavigatorPanel.java
Comment 7 Andrew Korostelev 2006-10-03 16:34:45 UTC 
*** Issue 86392 has been marked as a duplicate of this issue. ***
Comment 8 Andrew Korostelev 2006-10-03 16:40:01 UTC 
This bug is currently used to track status of Navogator window impact on uml
performance.
This problem wasn't solved in ide-coke_uml-061003_6.
see duplicate issue 86392 - opened Overview window reduces uml repformance
extrimely.
Comment 9 Andrew Korostelev 2006-10-04 13:39:25 UTC 
exact steps of this issue works well now (performance regression is not so
visible in ide-coke_uml-061004).
So mark this bug as fixed again after jyothivasa's request.
related issue 86392 and issue 86044 are still reproducible
Comment 10 Andrew Korostelev 2006-10-04 13:46:56 UTC 
verified in ide-coke_uml-061004
Navigator's impact on uml performance is now not so visible on exact steps used
in this issue.
Nevertheles uml performance with opened navigator window is worse then without it.
Another bugs are filed with more visible steps.