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 218496 - [73cat] CodeCompletion took 3279 ms.
Summary: [73cat] CodeCompletion took 3279 ms.
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Expression Language (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Marek Fukala
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2012-09-18 04:05 UTC by misterm
Modified: 2012-10-10 12:55 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 192509

Attachments
nps snapshot (50.77 KB, application/nps)
2012-09-18 04:05 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-09-18 04:05:45 UTC 
This bug was originally marked as duplicate of bug 185294, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 20120914-1d2f1a14b692)
VM: Java HotSpot(TM) 64-Bit Server VM, 21.1-b02, Java(TM) SE Runtime Environment, 1.7.0_01-b08
OS: Windows 7
Maximum slowness yet reported was 3279 ms, average is 3279
Comment 1 misterm 2012-09-18 04:05:48 UTC 
Created attachment 124484 [details]
nps snapshot
Comment 2 Jan Lahoda 2012-09-18 10:59:06 UTC 
Tonda, a particular reason to believe this has anything to do with java.hints?

What I see in the dump is 2517ms spent in code completion computation, out of which 2447ms is spent in ELCodeCompletionHandler. Out of that, almost 800ms seems to be spent in XML parsing, out of which about 650ms are spent in getting something from the lookup (out of which pretty big chunk appears to be spent in classloading). I suggest this to be evaluated by ELCodeCompletionHandler maintainers.
Comment 3 Antonin Nebuzelsky 2012-09-18 11:05:02 UTC 
(In reply to comment #2)
> Tonda, a particular reason to believe this has anything to do with java.hints?

Just the note from exception reporter that this is probably a duplicate of 185294.
Comment 4 Marek Fukala 2012-10-10 12:55:26 UTC 
The code triggered the facelets libraries initialization which takes some time. As this happens just once (then everything is cached) I'm closing the bug.