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: | CodeCompletion took 2832 ms. | ||
---|---|---|---|
Product: | webservices | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | Code | Assignee: | Denis Anisimov <ads> |
Status: | REOPENED --- | ||
Severity: | normal | CC: | alied, misterm, muellermi, toben |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | Dev | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 190344 |
Attachments: | nps snapshot |
Description
Exceptions Reporter
2012-07-02 15:26:37 UTC
Created attachment 121660 [details]
nps snapshot
The WS code completion is implemented via AsyncCompletionQuery. It means that all computational work is done in the separate dedicated thread. So UI is not blocked by the computational work. Code completion framework provides a way to cancel time consuming task. So user is able to cancel CC task at any time. Computation itself could take some significant time and it's not an issue. In this particular case CC thread spend most time on the lock acquisition for runUserTask() of TaskProcessor (not inside real computation logic). And as I already said there is a way to avoid waiting the CC result. >The WS code completion is implemented via AsyncCompletionQuery.
>It means that all computational work is done in the separate dedicated thread.
>So UI is not blocked by the computational work.
In fact, the UI is not frozen by the long running code completion.
But, it is the user waiting for CC. Thus, even technically not blocked, the user can't work - or can't use CC.
If we want the user not to use CC, then it is better to switch off this freature completely ;-)
|