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.
Summary: | Don't use UI thread when adding new files to project | ||
---|---|---|---|
Product: | cnd | Reporter: | Vladimir Kvashin <vkvashin> |
Component: | Project | Assignee: | Thomas Preisler <thp> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Vladimir Kvashin
2006-10-26 10:14:47 UTC
I think, it's P2, because significantly affect responsiveness and performance. And at the same time no any notification to user about long-time taks. Impl. comment: don't use Vector for big collections. Synchronized ArrayList is 2 times faster than Vector. seems, we can improve speed up by changing listener. now we have: for each new added file { inform all listeners that new file was added } => for listeners it´s impossible to estimate how many other calls it will have. we can do: create list of all new files for each listener { inform listener about added list of files } In this case we (code model part) could provide progress to indicate that some number of files is under parse. Although one problem still remains. ¨create list of all new files¨ is expensive => project system should enforce progress bar in infinite state as well for indicating some activity. And of course this phase should be moved out from UI thread. Yes, creating a queue of files being added and putting it into parser queue in a separate thread will improve sutuation a bit. But even when code model switched off at all, UI hangs for more than a minute when user adds 2000 files to a project. Now files are added to the project from a seperate thread. This fixes the major problem in this issue. There are other good suggestions in this bug report of how to improve performance. I will close this issue as dup of 76817 now the main issue has been fixed and deal with all performance issues at once. I don't believe these are so bad that they are p1 or p2. *** This issue has been marked as a duplicate of 76817 *** |