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 33395 - Internatiolization wizard do find of JavaDataObjects in awt-queue
Summary: Internatiolization wizard do find of JavaDataObjects in awt-queue
Status: VERIFIED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: I18N (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords: PERFORMANCE, THREAD
Depends on:
Blocks:
 
Reported: 2003-05-05 15:21 UTC by pzajac
Modified: 2004-08-13 12:11 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
blocked awt-queue stacktrace (29.33 KB, text/plain)
2003-05-05 15:24 UTC, pzajac 		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 pzajac 2003-05-05 15:21:42 UTC 
Open internatiolization wizard. Click to add
source button. Select a huge  folder. I tried it
on openide/src.  Ide is blocked for many seconds.
Comment 1 pzajac 2003-05-05 15:24:39 UTC 
Created attachment 10219 [details]
blocked awt-queue stacktrace
Comment 2 _ pkuzel 2003-05-05 16:49:11 UTC 
It looks like you have 80 levels of nested folders, do you?

Anyway current strategy when descending to child folder is prefered
over scanning folder itself can be wrong. Further all tests are done
at DataObject level in spite of that they could be done at FS level.
The logi cannot be run in any other thread and it drives displyed UI.
Comment 3 Marian Petras 2004-01-27 10:44:17 UTC 
I will not be able to fix this bug in NetBeans 3.6 timeframe. It
requires large change of code and also changes of UI.

To improve the situation a little bit, I made some performance
improvements:
- changed the strategy so that Data Objects are searched using
  a breadth-search algorithm
- eliminated unnecessary type casting

Please try the next build and leave a note whether the improvements
are noticeable.
Comment 4 Ondrej Rypacek 2004-06-07 17:16:49 UTC 
Any test results after Marian's improvemenets?
Comment 5 Antonin Nebuzelsky 2004-06-09 17:19:29 UTC 
We consider this type of performance issues a P2. Upgrading.
Comment 6 Ondrej Rypacek 2004-06-14 14:32:07 UTC 
I tried that with the latest build and openide/src and the responce
time was less then 1s. On my old computer (700Mhz), this took <2s. 

Are there any responsiveness criteriea that justify this as a bug?
Comment 7 pzajac 2004-06-14 15:39:32 UTC 
v