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.
Summary: | Time to switch between xsd files while Navigator is in Schema View mode exceeds 100 ms | ||
---|---|---|---|
Product: | xml | Reporter: | Alexander Kouznetsov <mrkam> |
Component: | Schema | Assignee: | Samaresh Panda <samaresh> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | michaelnazarov, tonybeckham |
Priority: | P2 | Keywords: | PERFORMANCE, TEST |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://test4u.czech.sun.com/test4u-users/nb-perfteam/results/20080226190100/spb-perf-lin2/testrun_080226-210549/testbag_10/htmlresults/suites/TEST-gui.EPMeasureActions3.html#gui.actions.NavigatorSchemaViewMode.Schema%20Navigator%20Schema%20View%20mode | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Alexander Kouznetsov
2008-02-27 17:27:03 UTC
Can you provide some more info? 25sec is a long time. Are you sure about the tests? Also, can you help us reproduce it manually? The test seems to be ok, I got 13 seconds manually on my computer which is much better than recommended configuration. The scenario is as following: 1. Expand SOATestProject node in Projects view 2. Expand Process Files node 3. Select batch.xsd node 4. Switch combobox in Navigator panel in Schema View 5. Select fields.xsd node * EXPECTED RESULT: Navigator panel updated with Schema View within 100 ms http://wiki.netbeans.org/TS_60_Performance#section-TS_60_Performance-SOAXMLFunctionality For me this action takes about 1 sec. I know it is greater than the 100ms barrier but not anywhere close to 25sec. Product Version: NetBeans IDE Dev (Build 200802270005) Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19 System: Linux version 2.6.22-14-generic running on i386; UTF-8; en_US (nb) Well, this is issue, but not exactly in area as specified in spec. First of all we are dealing with huge amount of data in this test case and we can't set 100ms limit for data of arbitrary size. The bigger data the longer time required. Switching itself doesn't required much time but followed recalculation does, so there are two ways to solve this: claim this issue not as defect but as enhancement and provide something like progress bar for such long operations in the future; or keep kind of cache and skip recalculating each time but use already existing data. In last case progress bar will need also for the first time, so I prefer first case. Finally: set type to enhancement and keep or even increase priority. Implement after beta. Fix integrated. http://hg.netbeans.org/main?cmd=changeset;node=0a0690fa388b http://hg.netbeans.org/main?cmd=changeset;node=c653d18df529 http://hg.netbeans.org/main?cmd=changeset;node=eb0bbbc0fc1d Both design view and schema view will respond with a please wait similar to java classes. Fix Verified Product Version: NetBeans IDE Dev (Build 200803051205) Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-119 System: Mac OS X version 10.5.2 running on i386; MacRoman; en_US (nb) |