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 210737 - LowPerformance took 54168 ms.
Summary: LowPerformance took 54168 ms.
Status: NEW
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Marek Fukala
URL:
Keywords: PERFORMANCE
: 209811 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-04-05 01:56 UTC by dwuysan
Modified: 2016-02-01 08:27 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 186688

Attachments
nps snapshot (795.20 KB, application/nps)
2012-04-05 01:57 UTC, dwuysan 		Details
nps snapshot (173.63 KB, application/nps)
2013-09-17 08:21 UTC, davideconsonni 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dwuysan 2012-04-05 01:56:53 UTC 
This bug was originally marked as duplicate of bug 183792, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.1.1 (Build 201202271535)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.0-b19, Java(TM) SE Runtime Environment, 1.7.0_04-ea-b18
OS: Linux

User Comments:
dwuysan: Editing in .properties files and JSP files are really really slow.



Maximum slowness yet reported was 54168 ms, average is 54168
Comment 1 dwuysan 2012-04-05 01:57:21 UTC 
Created attachment 117850 [details]
nps snapshot
Comment 2 davideconsonni 2013-09-17 08:21:06 UTC 
Created attachment 140161 [details]
nps snapshot

opening a jsp
Comment 3 Martin Janicek 2013-12-17 12:43:20 UTC 
*** Bug 209811 has been marked as a duplicate of this bug. ***
Comment 4 Marek Fukala 2014-07-30 11:34:19 UTC 
JspDataObject.getFileEncoding() can be really slow.

Since 2005, there's an optimisation (o.n.m.web.jspparser.FastOpenInfoParser) which quickly determines the JSP file encoding without running the 'true' jsp parser. However under some circumstances this parser can't properly provide the encoding and then it fallbacks to the jsp parser. This however means the thread is blocked until the jsp parsing thread finishes its work, which may take very long time.

Even in the case when the true jsp parser is used to obtain the file encoding, the call doesn't need to necessarily be very slow. In most cases, just the first jsp parser call is slow, subsequent calls are not that bad.

I'm not sure if it is worth of the effort to address this problem so I won't attempt to fix it now, but keep it open so we can track it.