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 220370 - Slower code completion window in comparison with 7.2.x
Summary: Slower code completion window in comparison with 7.2.x
Status: RESOLVED DUPLICATE of bug 219507
Alias: None
Product: editor
Classification: Unclassified
Component: Completion & Templates (show other bugs)
Version: 7.3
Hardware: PC Linux
: P3 normal (vote)
Assignee: Dusan Balek
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2012-10-18 14:14 UTC by Vladimir Riha
Modified: 2012-11-14 14:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
721 snapshot (13.23 KB, application/octet-stream)
2012-10-18 14:14 UTC, Vladimir Riha
Details
7.3 NetBeans IDE Dev (Build 201210180002) snapshot (13.43 KB, application/octet-stream)
2012-10-18 14:14 UTC, Vladimir Riha
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2012-10-18 14:14:08 UTC
Created attachment 126145 [details]
721 snapshot

Seems to me that code completion window is quite slower in 7.3 then in 7.2.1. The difference is more significant if you type (I tried JS, PHP and HTML) and the window is updated as you typed. With 7.3 I have to even "wait" sometimes so I can e.g. confirm item from cc window.

The attached snapshots are from single code completion invocation. I'm not sure how much representative it is, I can provide more information if needed.

Thanks
Comment 1 Vladimir Riha 2012-10-18 14:14:41 UTC
Created attachment 126146 [details]
7.3 NetBeans IDE Dev (Build 201210180002) snapshot
Comment 2 Petr Cyhelsky 2012-11-01 08:54:22 UTC
org.netbeans.modules.editor.completion.CompletionLayoutPopup.showAlongOccupiedBounds()  is dramatically slower in 7.3 - 30,5ms vs 639 ms

please investigate

according to reporter both ide's were run on the same jdk.
Comment 3 Dusan Balek 2012-11-14 14:47:11 UTC
Already fixed.

*** This bug has been marked as a duplicate of bug 219507 ***