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 14679 - JSP editor performance problem
Summary: JSP editor performance problem
Status: VERIFIED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Marek Fukala
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2001-08-22 16:19 UTC by Damian Frach
Modified: 2004-10-14 11:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
the OptimizeIt output 1 (73.15 KB, text/plain)
2001-08-22 16:21 UTC, Damian Frach
Details
the OptimizeIt output 2 (891.38 KB, text/plain)
2001-08-22 16:22 UTC, Damian Frach
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Damian Frach 2001-08-22 16:19:52 UTC
JSP editing is slow (simple character addings). 

JDK 1.3.1; 700MHz Intel; win2000

JSP - 400 lines; 114 columns
("<P><A href="/hello.jsp">Hello</A></P> <P><A href="/hello.jsp">Hello</A></P> 
<P><A href="/hello.jsp">Hello</A></P>
")

Looks like problem in JspMultiSyntax.canBeHostDelimiter().

More info in attached files from the OptimizeIt.
Comment 1 Damian Frach 2001-08-22 16:21:08 UTC
Created attachment 2272 [details]
the OptimizeIt output 1
Comment 2 Damian Frach 2001-08-22 16:22:28 UTC
Created attachment 2273 [details]
the OptimizeIt output 2
Comment 3 Damian Frach 2001-08-23 15:13:18 UTC
It looks like, the canBeHostDelimiter method is called 154000 times 
during a simple 10 spaces.
Comment 4 Jan Chalupa 2001-11-27 17:37:11 UTC
Target milestone -> 3.3.1.
Comment 5 Petr Jiricka 2002-05-07 11:45:24 UTC
A likely reason is the fact that the whole file is parsed 
under some circumstances, not only the changed part.
Comment 6 Marek Grummich 2002-07-22 12:11:43 UTC
Set target milestone to TBD
Comment 7 Marek Grummich 2002-07-22 12:21:40 UTC
Set target milestone to TBD
Comment 8 _ rkubacki 2003-01-13 12:19:00 UTC
Tegal planning
Comment 9 _ rkubacki 2003-01-23 13:25:27 UTC
It might be related to issue #30000. Also we can check how it behaves
with new parser
Comment 10 Petr Pisl 2004-02-11 09:15:24 UTC
This is not easy to fix it. And any change in JspMultiSyntax is very
risky. So I think we will not fix this for 3.6
Comment 11 Marek Fukala 2004-08-18 13:01:30 UTC
fixed - The causes of the problem were indentation engine and code
completion demanding tasks performed after each typed character in the
editor.

The performance problem was especially apparent when editing in a
large block of HTML code. When there were JSP tags or scriptlets
around the edited place the performance was not so terrible.

The fix could possibly affect jsp code completion autopopup and JSP
files reformating and indentation. 

Checking in JspSyntaxSupport.java;
/cvs/web/jspsyntax/src/org/netbeans/modules/web/core/syntax/JspSyntaxSupport.java,v
 <--  JspSyntaxSupport.java
new revision: 1.37; previous revision: 1.36
done
Checking in JspFormatter.java;
/cvs/web/jspsyntax/src/org/netbeans/modules/web/core/syntax/JspFormatter.java,v
 <--  JspFormatter.java
new revision: 1.5; previous revision: 1.4
done
Comment 12 Martin Schovanek 2004-10-14 11:27:16 UTC
V