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.
This issue is the place to collect requirements from all Gavotte functional team to performance measurements. If you do have in mind some action or set of actions(specific to your functional area, BPEL, XSLT, Identity, etc .. ) that should be measured please describe it below.
For the BPEL team we have the following preliminary requirements for performance measurements: - Time required to deploy/undeploy/build projects. The deployment time is involved in the PBS criteria and has to be controlled. Sample or specifically developed projects may be used for measurements. Some common actions for the complex projects (also partially involved in PBS criteria): - Time required to create new and open existing projects - Time required to open complex and empty diagrams - Performance when scrolling diagrams, dragging activities over complex diagrams and creating new activities We are also interested in memory consumption required to open complex projects and diagrams. Memory leakage possible when doing these actions (reopening diagrams and projects, compiling project, debugging) is also quite important. I understand these are quite high level usecases but if we continue with them our team can create the requried sample projects, diagrams, etc to be used by the performance team.
REQUEST FROM Gavotte P-Team(Actually from Tim C) 1. Absolute performance measurements (not percentages based on previous release measurements) 2. Measurements should be done on the minimum configuration and on the recommended configuration machines.
The Edit Web Service Attributes action in the web service provider/client invokes a set of panels (customization WSIT and AM) in enterprise pack. We need to measure the time it takes for the panel to show up with all these panels added and make sure it is within the accepted boundary.
The most important actions we want to measure * IDE startup time * Memory consumption with all started servers * Project creation (BPEL module) * Deploy build project * Undeploy project * Build project * Open existing BPEL project * Open empty diagram for the complex projects * Open complex diagram for the complex projects * Scrolling diagrams performance for the complex projects * Dragging activities over complex diagrams * Creating new activities * Memory consumption required to open complex projects and diagrams * Add new BPEL process to BPEL module * Add new WSDL document to BPEL module * Add new XML document to BPEL module * Add new XML schema to BPEL module * Project creation (Composite application) * Open existing XML schema * Switch between view in XML schema * Using Design Pattern in XML schema * Using UNDO operation in XML schema * Validation operation in XML schema * Using autocompletion in XML schema
http://www.netbeans.org/issues/show_bug.cgi?id=90882 The validation takes currently too much time. It seems to be a performance regression. The TRS sample validation currently takes around 17 seconds on my 3Gh, 1Gb memory machine. This is not acceptable for a project of TRS size. Moreover for long running tasks like this some indication is required. See http://performance.netbeans.org/responsiveness/whatisresponsiveness.html for example.
A list of XML Tools actions that might be of interest in terms of performance: - open messages.xsd (the file which is a part of HL7 schema) in XML Editor; - in Schema view perform Refactor/Rename SI simple type. The type is defined in datatypes.xsd file which is part of HL7 schema; - Refactor/Undo Rename for the schema and type mentioned in the previous scenario; - apply Salami Slice design pattern to OTA_TravelItinerary.xsd schema; - open OTA schema, switch to Design view and add a new global element into the schema; - delete the newly added element from the schema in Design view.
Testcase from Netbeans performance test suite Measure Actions 1 Open Java file (20kB) 2 Open Txt file (20kB) 3 Open Xml file (20kB) 4 Open JSP file 5 Select GUI Forms category in New File 6 Select XML category in New File 7 Create Java Application project 8 Create Java Class Library project 9 Create Web Application project 10 Create Java Project with Existing sources 11 Create Module Project 12 Close Java Application project Measure Dialogues 1 Java Platform Manager open 2 Server Manager open 3 Options dialog open 4 New Project dialog open 5 New File dialog open 6 Update Center wizard open 7 NB Project Properties window open 8 Web Project Properties window open 9 Library Manager open Measure Menus 1 File main menu 2 Edit main menu 3 Build main menu 4 Run main menu 5 Help main menu 6 View | Editors main menu 7 View | Toolbars main menu 8 Run | Run File main menu 9 Xml file node popup in Projects View
Additional XML measurements to be automated - Navigator (Design View) (Single click on a schema, renders the navigator view for the schema.) - Navigator (Schema View) (Single click on a schema, renders the navigator view for the schema.) - Schema View (Right click on a schema and click on 'Open'. Opens the schema in Schema view.) - Design View ( Switch to design view from Schema view -- user will not be kept waiting for 10 seconds to see the first visual feedback)
Additional testing for Gavotte. - open schema (Schema View opens) - switch to Source View - modify (add some element) - switch to Schema View - modify - switch to Tree View - modify - switch to Design View - modify - switch to Source View
It is not actual anymore. Closing.