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 268747 - Add self-profiling to standard release process
Summary: Add self-profiling to standard release process
Status: NEW
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: Dev
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-30 15:27 UTC by NukemBy
Modified: 2016-10-30 15:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description NukemBy 2016-10-30 15:27:04 UTC
This is not a bug, but rather a "message to NetBeans product owners".

New NB Release 8.2 which was released a month ago is as "laggy and slow" as usual. Unfortunately performance on real production projects with large codebase is close to unacceptable:
- initial loading of project (background scan) takes looong time - I have to wait for 10 minutes before can start working (some functionality is not available until bg-scan finishes)
- while editing java code, syntax highlight refreshes in a minute or so
- editing of large JS files is just laggy - IDE freezes once per few seconds
- debugging a Java process - is slow because of slow evaluation of variables
- some user actions get visual result in 30+ seconds ...

I've been self-profiling NetBeans during last month with the aim to make my life easier. I've found and fixed most of the annoying issues in my local dev build and my findings say to me that NB team either just does not care about performance, or does not know about such good thing as Self Profiler or ... do not have time for performance analysis.

Quick and responsive IDE is essential thing for developers. "Slow and laggy" does not work even if there is some cool functionality present.

Please add self-profiling of NB on large codebases into standard release cycle.

All my findings are already reported as individual issues. I've attached hacky-patches to address them.