Category:Performance

(Difference between revisions)
(The Performance Doublethink)
(The Performance Doublethink)
Line 5: Line 5:
The [[performance]] team plays two roles. On one side it acts as a guardian against regressions in consumption of various resources. On the other it needs to pro-actively seek and drive general improvements in overall architecture of the application. Mixing these two roles is not easy and may sometimes be perceived as pathological signs of [[doublethink]].
The [[performance]] team plays two roles. On one side it acts as a guardian against regressions in consumption of various resources. On the other it needs to pro-actively seek and drive general improvements in overall architecture of the application. Mixing these two roles is not easy and may sometimes be perceived as pathological signs of [[doublethink]].
-
TBD: The QA side with [[BugPriorityGuidelines|Bug priority guidelines]]
+
As part of improving the quality the [[performance]] team seeks for new ways to identify [[UI responsiveness]] problems, [[FitnessMemoryLeaks|memory leaks]] and suboptimal implementations. Various intricate [[Category:Performance:ToolsAndTests|tools and methods]] has been invented to identify the actual end user problems (most notably the [[Slowness Detector]]), be notified about them (in cooperation with [[ReportExceptionProject]]) and have enough information to reproduce them (thanks to [[UIGesturesCollector]]). [[Performance]] problems are then processed and classified according to general quality [[BugPriorityGuidelines|bug priority guidelines]].
 +
 
 +
The quality effort of [[performance]] team is always driven in boundaries of two important assumptions:
 +
# make sure we always improve something
 +
# identify and prevent regression
 +
By following these two simple constrains we managed to deliver [[Category:Performance:Improvements|visible improvements]] in spite of doing ''just'' small steps one by one. Of course we need to write [[Category:Performance:ToolsAndTests|a lot of tests]], execute them regularly and also have a statistical framework to [[FitnessViaStandardDeviation|notify us about exceptional states]] as soon as they appear.
TBD. [[Fitness|Development page]] - the development plan for most recent release.
TBD. [[Fitness|Development page]] - the development plan for most recent release.

Revision as of 12:59, 19 February 2010

This is the home page for NetBeans performance work. It provides introduction to the world of performance and enlists various other performance related pages grouped into appropriate (sub)categories.

The Performance Doublethink

The performance team plays two roles. On one side it acts as a guardian against regressions in consumption of various resources. On the other it needs to pro-actively seek and drive general improvements in overall architecture of the application. Mixing these two roles is not easy and may sometimes be perceived as pathological signs of doublethink.

As part of improving the quality the performance team seeks for new ways to identify UI responsiveness problems, memory leaks and suboptimal implementations. Various intricate has been invented to identify the actual end user problems (most notably the Slowness Detector), be notified about them (in cooperation with ReportExceptionProject) and have enough information to reproduce them (thanks to UIGesturesCollector). Performance problems are then processed and classified according to general quality bug priority guidelines.

The quality effort of performance team is always driven in boundaries of two important assumptions:

  1. make sure we always improve something
  2. identify and prevent regression

By following these two simple constrains we managed to deliver in spite of doing just small steps one by one. Of course we need to write, execute them regularly and also have a statistical framework to notify us about exceptional states as soon as they appear.

TBD. Development page - the development plan for most recent release.

Various Links

Here is an overview of all wiki pages related to NetBeans performance. See the genearal pages or inspect subcategories for specific performance aspects (including How can I fix memory leaks?, How can I profile NetBeans?, etc.).

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