NB61PerfPlan

Plan for NB 6.1 Performance Improvements

This is an implementation plan for performance improvements targeted for NetBeans 6.1 release. It covers work done by the performance team and some important issues solved by other teams, but still not quite all performance work done for 6.1 by all developers.

For an overview of what's being done for 6.1 see the list of planned improvements.

Contents


Important NB 6.1 Dates

  • feature freeze - February 25 (6.1 M2)
  • code freeze - March 31
  • final release - April 21

See also NB 6.1 milestones.

Milestones

The plan is divided into several milestones; the first one matches the official NetBeans 6.1 M1. The paragraph under each milestone describes what should be done (finished) by the date of the milestone. The plan is checked and updated weekly (on Monday).

January 14 (M1)

  • Image:yes_NB61PerfPlan.png (Yarda) Project opening does not block IDE startup - IZ 108120
  • P1: Prefer main project TBD
  • Image:yes_NB61PerfPlan.png (Radek) Master FS optimizations (do not delegate to embedded FS) - IZ 123542, see also FileSystems
  • Image:yes_NB61PerfPlan.png (Radek, Yarda) Lightweight file locking (faster file deletion and first file modification in editor, especially in deep file hierarchies) - IZ 106128
  • [[File:]] (with incomplete or not up-to-date metadata, so e.g. during scanning after startup)
  • done without UI that informs the user about incomplete results - TBD later after used for some time by people
  • need Fast Track API review
  • [[File:]]
  • replace existing build with new one and keep userdir P1
  • also during development when API Support updates the shared dir P1
  • talk to installer
  • Image:yes_NB61PerfPlan.png (Yarda, Tomas M.) Saving project properties not in AWT event queue thread - IZ 91291
  • both j2se and web projects
  • done for newly created pages, TODO an action for existing pages
  • Image:yes_NB61PerfPlan.png VW: Improve page flow editor opening (avoiding unnecessary page syncing) - IZ 123534
  • UI responsiveness of opening VW pages
  • Image:yes_NB61PerfPlan.png (Quy) Wait cursor - IZ 124928
  • Image:yes_NB61PerfPlan.png (Peter Zavadsky) Show 'Loading, please wait...' message for all pages opening - IZ 123411
  • Image:yes_NB61PerfPlan.png (Peter Zavadsky) VW: Only open the active page after startup - IZ 124931

January 28

  • Computed, shown, now we need to turn it into a "trigger warning"
  • Once made available, other should comment
  • Image:yes_NB61PerfPlan.png (QE) Comparative Dashboard update - latest results
  • Image:yes_NB61PerfPlan.png (Jirka) Prototypes of entry points for FoD (all types of P1 entry points)
  • no point in Tools/Options yet; Jarda: working actions
  • FoD postponed after 6.1 ...
  • Image:yes_NB61PerfPlan.png (Jarda) Cache for module config files (startup)
  • Image:yes_NB61PerfPlan.png (Jarda) Optimizing caches saving not to block startup and shutdown (e.g. layer cache, resources cache)
  • Image:yes_NB61PerfPlan.png (John Baker) VW: Caching table metadata not to connect to database during page open - IZ 123537
  • Java editor improvements
  • Image:yes_NB61PerfPlan.png (Jan Lahoda) Navigator parsing speedup - faster response on file open/switch/change
  • Image:yes_NB61PerfPlan.png (Tomas Zezula) Partial reparse of java files - for isolated changes reparsing only the affected method

February 11

  • [[File:]], announce
  • Image:yes_NB61PerfPlan.png (QE) BlackListed Class Logger (to watch classes loaded during startup)
  • (Pavel) Update on Windows / IO slowness
  • Additional optimization of lazy project opening
  • Image:yes_NB61PerfPlan.png (Milan) New API integrated - IZ 124980
  • (Tomas Z.) Global CP created and scanned after all projects opened
  • (Pavel) Go to Type dialog working with full CP after all projects opened
  • (QE) Tests Migration and Infrastructure changes because of migration to Mercurial
  • Image:yes_NB61PerfPlan.png (Tomas M., Jarda) Automated unit tests for jsp parser
  • Image:yes_NB61PerfPlan.png (Tomas M.) JSP parser caching fixes
  • Image:yes_NB61PerfPlan.png (QE) Why 6.1 occupies more memory than 6.0, is it due to caches? No it's IZ 126206
  • Image:yes_NB61PerfPlan.png (QE) measure cold startup, four configurations ready, machine set up already, we do not have viewer and data will be sent by mail, later visible on some website


February 25 (M2)

  • (Pavel) Analysis of overall slowness of Windows (mainly I/O related)
  • Image:yes_NB61PerfPlan.png some tests for single byte writes and File.isDirectory() calls - IZ 65135
  • comparative measuring of cold start and project opening/scanning on Windows and Linux (on the same HW)
  • Image:yes_NB61PerfPlan.png (Pavel) Go to Type dialog working with full CP after all projects opened
  • UI change - don't show "not found" until all scanning finished
  • update on possible scanning task interruption
  • Image:yes_NB61PerfPlan.png (Tomas M.) Background reparse - immediate cache updates after CP changes for code completion
  • Image:yes_NB61PerfPlan.png (Tomas M.) Eliminate code duplication in projects (part I) - IZ 126741
  • (QE) Variance calculation: create "trigger warning", relative normalized variance - easy, maybe one graph for value+variance
  • Image:yes_NB61PerfPlan.png (QE) VisualWeb measuring
  • (QE) Update on progress writing memory leaks, something written for Visual Web, not integrated. Some more tests to come soon.

March 10

  • Image:yes_NB61PerfPlan.png (Jarda) Ensure responsive switching over multiple tabs (window system)
  • (Jarda) Make repetitive actions in explorer (browsing, selections) fluent (actions system)
  • Image:yes_NB61PerfPlan.png (Jarda) Slow switching between files in editor or changing selection in Explorer (due to non-scaling listeners)
  • Image:yes_NB61PerfPlan.png P2: Fix most offending listeners in tab switching (especially noticeable in full IDE)
  • Image:yes_NB61PerfPlan.png (Pavel) Eliminate single byte reads/writes in FileInputStream/FileOutputStream - IZ 129286
  • (Pavel) Compare single bytes read/writes of 6.0 to current state
  • [[File:]] (IO touches)

March 24

  • (Jarda) Run tests on memory leaks regularly (e.g. commit validation): fix own issues, ask others to fix their, remeasure the real state
  • problems with leaks from AWT and other parts of the system
  • (Jarda) Speedup startup with opened editor
  • way to improve that with enabled welcome screen IZ 130123
  • speed up to enable as soon as editor initialization is, at least partially, done out of AWT thread


Long Running Tasks

These tasks are being worked on but have no planned deadline.

  • (QE) Test spec update, tests maintenance, extending test Suite, VM Ware image usage, etc...
  • (All) Find memory leaks in common areas - to make sure basic open/edit/save/compile/debug/test scenarios in main project types do not create major leaks in key data structures; should be covered by tests
  • (Quy) Memory leak fixes in Visual Web - IZ 123530
  • (Tomas M.) Eliminate code duplication in projects (part I - nearly done, part II - mainly related to project classpath) - IZ 122883, IZ 126741

Tasks not yet included in the plan

  • P3: Analyze disk access during common operations like expanding a package - to be able to optimize for network and slow filesystems
  • P3: Improve opening of UML diagrams (a lot of time spent in finding in model in diagrams with many connections) - IZ 123518
  • P3: Improve performance reverse engineering a java project into the same UML project more than once - IZ 123522
  • P3: Improve response time of UML explorer (selecting multiple nodes, invoking context menu) - IZ 123523

Dropped tasks (postponed after 6.1)

These tasks were originally considered for 6.1 but eventually dropped.

  • Feature on Demand - decided to postpone after 6.1 - the startup gain is not that big after all, it represents quite some work (would have to stop much of other work), it is risky and controversial - simply a too big thing for 6.1
  • P3: Avoid initial JDK classes scanning when creating/opening first project.
  • P2: Specific memory optimizations (JSP tag libs)
  • two pages do not share the same tag libraries, they create new memory structures
  • hard as each page can have own prefix and it is currently hardcoded in constructor
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo