See NPS snapshots in Exception Reporter.
Caused by very slow Windows disk IO
FileUtil.toFileObject() ~ 22ms
FileObject.getFileObject() ~ 15ms
Since these are called quite frequently during computing the current file dependencies graph the result is that the completion is slow.
Easiest way to fix this problem is to cache the dependencies graph for the edited file and invalidate it only if the index result changes (some of the deps. changed).
I'm going to do some css editor redesign into the next release so I'll address this issue later.
Created attachment 107721 [details]
Well known issue with very slow code completion, please fix it.
(In reply to comment #3)
> Created an attachment (id=107721) [details]
> nps snapshot
> Well known issue with very slow code completion, please fix it.
Just for curiosity the snapshot has nothing to do with css, it shows some java completion stuff.
I havent' found a single snapshot from the 50 duplicates showing css completion. There's something very rotten in the categorizing algorithm.
Marek, I downloaded couple of them without any problem. Could you report issue you are facing into ide/Report Exception ? Also please add you browser type/version info there please. Thanks in advance.
(In reply to comment #6)
> Marek, I downloaded couple of them without any problem. Could you report issue
> you are facing into ide/Report Exception ? Also please add you browser
> type/version info there please. Thanks in advance.
??? I was referring to the fact that the snapshots shows anything but css completion in the "Code Completion" thread. So how come all the reports are considered as duplicates of this issue??? (the original Dusan's snapshot really shows css completion performance problem)
I finally found two reports showing the problem of the CSS completion as described in comment #1.
I've created a new issue 198337 - Slow CSS code completion - CssIndex.getAllDependenciesGraph() and I'm going to reassign this one to Marian Mirilovis who is IMHO responsible for the exception reporter categorization mechanism.
Mariane, I'm sorry but I can do nothing with the issue since 99% of the reports are false duplicates. Thanks for resolving this somehow.
In my case, I've seen all the slowness reports for xslt completion going here, but didn't know how to re-assign the exception to some other bug report (and to remove assignment to this one).
Tomas, I expect the problem with recognition of duplicates for Slow Code Completion is already solved, isn't it ?
new reports are still coming, would anyone please check what is the root cause?
Still not fixed. Please check out http://statistics.netbeans.org/analytics/exception.do?id=765075
and http://statistics.netbeans.org/analytics/detail.do?id=178059 for more information.
New issue #250360 was created for report: http://statistics.netbeans.org/analytics/exception.do?id=765075
NetBeans Error Report Upload Complete
It has now been added to the database with id #840167. It has been classified as a duplicate of report #178059.
This bug was already fixed.
Please update your build of NetBeans to the latest build of 7.0.1 where bug #197270 is fixed. If you are already using a newer build and your report meets certain criteria a new bug will be filed automatically.
Bug seems not to be fixed so far *** reopened ***