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 205236 - Jsp Editor slow and high cpu usage
Summary: Jsp Editor slow and high cpu usage
Status: CLOSED INCOMPLETE
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP Parser (show other bugs)
Version: 7.0.1
Hardware: PC Windows XP
: P1 normal (vote)
Assignee: issues@javaee
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2011-11-17 09:15 UTC by mithunrajs
Modified: 2011-11-28 12:03 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Profiler Snapshot (20.62 KB, application/octet-stream)
2011-11-17 09:15 UTC, mithunrajs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mithunrajs 2011-11-17 09:15:21 UTC
Created attachment 113281 [details]
Profiler Snapshot

When editing  a JSP file, each keystroke makes the editor extremely slow to respond. Also CPU usage for 'netbeans.exe' rises to 50-70% on each keystroke and remains there. It takes a more than a 3-4 minutes to come back to normal. My struts project contains around 3500 jsp files. I had only a 3 or 4 jsp files open in the editor at the time. My settings are given below

Netbeans: 7.0.1 (all updates applied)
Tomcat: 7.0.22
Java: jdk6u29

Web Project
compile on save - enabled
Deploy on save - disabled
Comment 1 Petr Jiricka 2011-11-17 20:52:40 UTC
Thanks for the specific report, we'll take a look.
Comment 2 Petr Cyhelsky 2011-11-21 10:48:28 UTC
Are you sure this is the correct snapshot? It seems there isn't much activity recorded in the snapshot, AWT is not blocked and generally there isn't much CPU activity. Maybe it would be good to try to lower the timings for taking slowness report and report the resulting slownesses... see http://wiki.netbeans.org/FitnessViaPostMortem for details on how to set the thresholds.
Comment 3 Marian Mirilovic 2011-11-22 09:03:40 UTC
(In reply to comment #2)
> Are you sure this is the correct snapshot? It seems there isn't much activity
> recorded in the snapshot, AWT is not blocked and generally there isn't much CPU
> activity. Maybe it would be good to try to lower the timings for taking
> slowness report and report the resulting slownesses... see
> http://wiki.netbeans.org/FitnessViaPostMortem for details on how to set the
> thresholds.

Without requested information we can do nothing, sorry . Once you'll provide the data please reopen. Thanks in advance.
Comment 4 Marian Mirilovic 2011-11-28 12:03:32 UTC
v/closed