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 262601 - [newcodemodel] Performance degradation in find usages
Summary: [newcodemodel] Performance degradation in find usages
Status: RESOLVED INVALID
Alias: None
Product: cnd
Classification: Unclassified
Component: Code Model (show other bugs)
Version: 8.2
Hardware: PC Solaris
: P1 normal (vote)
Assignee: Vladimir Voskresensky
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2016-06-28 12:57 UTC by Alexander Simon
Modified: 2016-07-05 12:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
hot-spot of find usages "from Anchor.get()", firefox, js/src/jsapi.h (14.74 KB, text/html)
2016-06-28 13:05 UTC, Alexander Simon
Details
hot-spot of find usages "from Anchor.get()", firefox, js/src/jsapi.h (16.12 KB, text/html)
2016-06-28 14:34 UTC, Alexander Simon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Simon 2016-06-28 12:57:03 UTC
Find usages of widespread symbol has a several regressions.
1. 37% regression after migration on Java 8 (02/13/16)
2. 47% regression after switching on PTH (03/19/16)
3. 38% regression after migration on Clank 3.8 (06/17/16)
Totaly regression is 214% (3.14 times) since 01/13/16
Comment 1 Alexander Simon 2016-06-28 13:05:29 UTC
Created attachment 160182 [details]
hot-spot of find usages "from Anchor.get()", firefox, js/src/jsapi.h
Comment 2 Vladimir Voskresensky 2016-06-28 13:45:13 UTC
I assume it is the result of pushed new not-yet-optimized clank 3.8
Alexander, could you investigate, please, what is the main hotspot in 3.8 comparing to existing 3.6?
Thanks
Comment 3 Vladimir Voskresensky 2016-06-28 13:49:07 UTC
sorry. I have missed your messages...
Comment 4 Alexander Simon 2016-06-28 14:34:01 UTC
Created attachment 160186 [details]
hot-spot of find usages "from Anchor.get()", firefox, js/src/jsapi.h

code base is before migration on 3.8 (hg update f5e5aca1a7fb)
Comment 5 Vladimir Voskresensky 2016-07-05 12:53:12 UTC
Alexander found that problem was with incorrect memory settings for the test runs. Now it is fixed and result is 46 sec