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 222805 - [73cat] CodeCompletion took 3025 ms.
Summary: [73cat] CodeCompletion took 3025 ms.
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2012-11-27 10:27 UTC by misterm
Modified: 2012-11-29 02:33 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 195745

Attachments
nps snapshot (64.46 KB, application/nps)
2012-11-27 10:27 UTC, misterm 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description misterm 2012-11-27 10:27:04 UTC 
This issue was reported manually by misterm.
It already has 1 duplicates 


Build: NetBeans IDE Dev (Build 20121126-0a26cdb355e6)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.3-b01, Java(TM) SE Runtime Environment, 1.7.0_07-b11
OS: Windows 7
Maximum slowness yet reported was 3025 ms, average is 3025
Comment 1 misterm 2012-11-27 10:27:07 UTC 
Created attachment 128436 [details]
nps snapshot
Comment 2 Milos Kleint 2012-11-27 12:51:31 UTC 
https://hg.netbeans.org/core-main/rev/b58cf7b9ae02

makes sure there is only one evaluator created per MavenProject instance with the same lifecycle. that should improve the speed of the only obvious bottleneck place.

The rest appears to be contributed to by native IO processing..
Comment 3 Quality Engineering 2012-11-29 02:33:17 UTC 
Integrated into 'main-golden', will be available in build *201211290002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/b58cf7b9ae02
User: Milos Kleint <mkleint@netbeans.org>
Log: #222805 cache expression evaluator in MavenProject instance, both have the same lifecycle. if project gets reloaded a new evaluator will be created, otherwise we will reuse the same one all over again.