Hi Andy,
I measured the time it took XEmacs 21.4 (patch 8) running JDEE
2.2.9beta10 and sematic 1.4 to load some Java Swing files on a
128-megabyte Pentium III desktop running at 900 Mhz. The load time is
the time from an open file command to the time when the file becomes
editable and includes the time to fontify and bovinate the buffer. The
load time ranged from about 2 seconds for a 200-line file to about 15
seconds for a 5000-line file (see table below). On my machine,
fontification dominated the load time on large files. The parse time
(i.e., semantic bovinator time) was never more than a few seconds even
for a 5000-line file.
Based on my measurements and the fact that the user has a faster machine
than mine, the user should be seeing about a 2-3 second
load time for his "typical" 300-line Java files. I don't know why he is
seeing 20+ second load times. Perhaps, he has an old version of
semantic on his system. Recent versions of semantic have dramatically
slashed the time required to parse files and the time should drop even
further with the advent of the upcoming bison-like parser to be
included in semantic.
- Paul
File Size (lines) Load Time (seconds)
=========================================================================
CellEditor.java 117 2.1
Action.java 188 2.2
ActionMap.java 205 2.0
JRootPane.java 969 4.9
JTabbedPane.java 2010 6.5
JComponent.java 5112 15.0
> -----Original Message-----
> From: xemacs-beta-admin(a)xemacs.org
> [mailto:xemacs-beta-adminï¼ xemacs.org]On Behalf Of Tom Howland
> Sent: Friday, September 06, 2002 3:59 PM
> To: xemacs-beta(a)xemacs.org
> Subject: jde considered harmful
>
> As a long time fan of xemacs I implore whoever is responsible for
> putting together the xemacs distributions to please remove jde ... this
> package, as wonderful as it may be, makes editing java files so slow it
> is embarrassing.
>
> What is happening, I believe, is that the semantic bovinator is munching
> away all my cycles.
>
> For a typical 300 line java source file on my Dell 1 gigahertz 1
> gigabyte laptop running XP it takes a couple of seconds fontifying and
> then after the progress bar of fontification reaches the end. It just
> sits there sucking down cycles for perhaps 20 seconds more.
>