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:||at startup (nearly) no background tasks|
|Component:||Performance||Assignee:||Tomas Hurka <thurka>|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
Description zuhans 2008-07-03 18:33:25 UTC
hello, i run nb6.1 on winxp and on debian-lenny(testing). as you maybe know both are faster than 6.0 but on debian it's much faster than on winxp. i think, that there shouldn't be such a lot (background) processes during startup: all those project checkings and path checkings must not be during startup. in the beginning only those things should be done, that are essential for the ui-setup: * the menues should be there (e.g. i should be able to do a manual plugin-update-checking - i really want to do that by hand) * in the project overview only the names of the projects should be there. * maybe for those files, that are already open because of the last development-session some really necessary things should be done (so that i can work on them right away). the project dependencies and paths should only be checked when i use them the first time (with a little message-window that tells me what's going on). this would improve the startup-experience a lot - i think. greetings zuhans
Comment 1 lmw 2008-08-03 15:04:28 UTC
Hi, I agree with Zuhans.
Comment 2 nb_anm 2008-08-03 15:17:25 UTC
I think the check of dependencies should be improved, because it takes too much time at startup.
Comment 3 mithun_gonsalvez 2008-08-04 07:06:45 UTC
I Definitely agree... with Zuhans
Comment 4 Jan Becicka 2008-08-05 14:16:54 UTC
*** This issue has been marked as a duplicate of 133943 ***
Comment 5 zuhans 2008-08-07 09:21:40 UTC
i must say, that my issue is not a duplicate of 133943. because: i suggest to do (nearly) no scanning at all at startup.
Comment 6 dragginlord 2009-02-15 01:02:04 UTC
I agree, Netbeans should not scan projects at startup, only when a project is requested. This is a huge performance issue, and the primary reason it takes over 5 minutes for Netbeans 6.5 to load and be usable (during which it hogs %100 percent of my CPU). Eclipse takes a fraction of this time to load. If there was a way to prevent this right now I would most assuredly opt for it.