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.
Created attachment 114051 [details] Snapshot of IDE after closing connection to localhost Oracle db After accessing Localhost Oracle (URL="jdbc:oracle:thin:@localhost:1521:XE") with Oracle jdbc driver the IDE gets slugish; even after closing the connection. Attach snapshot since after closing the connection. Also I have a web application on Tomcat, in case it helps.
After investigation the snapshot I can see the only expensive operation what is eating 1/3 of CPU is tomcat.ServerLog$AnalyzingLineProcessor. Maybe someone from editor team might give a hint how to rid calling GlobalPathRegistry.findResource from output line analyzer. alied, could you attach also selfsampler<timestamp>.npss file which is located in your system temporary directory?
I'm experiencing the same problem connecting to an oracle db but I'm not using tomcat. After opening the connection in the db explorer (services panel) and executing a few queries the ide start getting very slow, memory usage goes at over 700MB and eventually it become so slow that it's unusable. I attach a snapshot taken while the IDE was extremely slow and a thread dump. Regards, Paolo.
Created attachment 114143 [details] jstack thread dump
Created attachment 114144 [details] Snapshot
Created attachment 114145 [details] Snapshot
Paolo, please don't mix two problems together. Let's solve Tomcat problem in this issue and open new issue for db one. Check also other reports for db performance and past your snapshots there if similar. Thanks
Created attachment 114160 [details] self sampler; 12/12/2011 14:20 The previously uploaded snapshot was 12/12/2011 13:07
Created attachment 114162 [details] self sampler; 12/12/2011 13:00
(In reply to comment #6) > Paolo, please don't mix two problems together. Let's solve Tomcat problem in > this issue and open new issue for db one. Check also other reports for db > performance and past your snapshots there if similar. Thanks Sorry, I thought it was the same defect because the symptoms are identical. I opened a new bug report: http://netbeans.org/bugzilla/show_bug.cgi?id=206396 Thanks, Paolo
Is there a lot of stack traces in the log? The slowness itself seems to be related to Maven project queries.
Created attachment 118339 [details] snapshot screenshot 1
Created attachment 118345 [details] snapshot screenshot 2 on the maven side apparently vast majority of time is spent in OS level filesystem calls (eg 4000 ms in lastModified check) - see screenshots technically the MavenForBinaryQueryImpl attempts to check the classpath url against the maven project's output directories to see if it's a match. It's only done on maven projects themselves, so the file:// protocol url belonged to the maven project. The occurence of the MavenProject loading is occurring conditionally, most probably the project in question was not opened, there was severe need to memory and cached Mavenproject instance were discarded (using softreference there afaik) or something unknown.
phejl, please advice how to proceed beyond pure analysis of the problem.
I suggest the tomcat output processor just marks all stacktrace like (or whatever the criteria is) likes as hyperlinks without first checking if the line is indeed clickable (can be found in projects) and only performs the check when someone actually clicks the hyperlink. That will speed up the processing significantly, AFAIK we've done the same in general maven output processing as well.
*** Bug 243861 has been marked as a duplicate of this bug. ***