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.
opening 10 files, NB 8s.+4s. of some background work when file is already opened but you can't start editing (total 12s.) vs Eclipse total 4s.; 50 files, NB 40s.+70s of background work (110s.) vs 25s. Eclipse. Also java files opening for comparison: 10 files NB 1-2s. vs Eclipse ~5s. 50 files NB 3-4s. vs Eclipse ~12s.
Could this be a duplicate of issue 142684?
Maybe - Oleg, could you please provide information about tested NB build? Thanks.
Awaiting details...
first measurement was for 20080801 today I've remeasured with 200808120201 (Full IDE) - results are the same. Windows XP java 1.6.0_10
This is not duplicate of issue 142684. Please specify: -the defect specification (what is the issue and why is it reported as a defect - regression?) -thread dumps - we can't even categorize the issue to proper component
Created attachment 67260 [details] dumps during files opening
Created attachment 67261 [details] dumps after files are opened but some background work is performed and IDE doens't respond
justification: as per Bug Priority Guidelines - significant scalability problem. In this case comparing to competing product. Data above is for recommended HW, P4 2.8GHz/1Gb RAM.
Oleg, next time set the correct MIME type, thanks.
Oleg, could you, please, describe how did you get the results? -- Is it a result of manual testing or from automated tests? If it is the result from a test, we need to know which test and how to run it. If it is the result from manual testing, where we can find a project used for measurements. Thanks.
that's manual measurements I'll send you a link to our project.
Thanks guys for looking into this.
We spent some time finding a solution for this but not very successfully. Looks like the work needed for all the files to open could be reduced if each file's tab opened in editor is not "activated" - only the last one. This requires some changes in window system (other file types might benefit from as well) - but the changes seem rather tricky and risky to do now, just before 6.5 code freeze. So unfortunately, fixing this for 6.5 does not seem to be an option (in current time frame). I'd suggest to lower the priority to P3 - it is not very typical to open as many JSP files at once, moreover - after startup this issue does not happen (only the last selected file is "activated" - i.e. fully loaded). There is no regression either. Still this should be fixed after 6.5. Oleg, do you agree with lowering priority? If not, we'll ask for a waiver for this issue. Thanks
Actually I haven't heard any complains from customers about that so I guess P3 is ok for now.
Will be fixed after 6.5.
I am moving this to the jsp editor.
I tried this again in the latest build of NB 6.8 on 44 JSPs from the JSP Examples sample project that is included with NetBeans, and the whole process took about 7 seconds (measured with stopwatch). I think this is reasonable, so I consider this fixed. If there are other measurements which suggest that this is still a problem, please reopen and attach the latest performance data. Thanks.