You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Rickard Öberg <ri...@xpedio.com> on 2001/08/07 16:34:36 UTC
Re: [Webwork-user] Re: Velocity and WebWork: speed speed and more speed
"Geir Magnusson Jr." wrote:
> > Ok, and now here's the good part:
> > running monthlist.vm on Catalina, a.k.a. Tomcat 4, takes about 30ms.
> >
> > Read again if you wish :-)
>
> <picking up jaw off of desk>
>
> I honestly will say, publicly, that I don't believe it :)
Well... me neither... but it's staring me in the face right now, and I
can rerun as many times as I want to..
One weird thing though:
The timings are all taken using a little WebWork action that internally
uses URLConnection to get the data. This is used so as to get proper
statistics by doing 100 hits at a time. Here's the weird part: when I
use IE5 I get the same results as the test program, but using Netscape
4.7 I get about 90-110ms instead of 30-50ms. Might be something weird in
how Netscape gets its data, but still...
> What hardware are you running on? I want to see if I can get my little
> jsp vs. vel tests to scale that way on my old P2-300, so if I know your
> rig, I can see if my results make sense.
P4, 933MHz, 512MB RAM, Win2KPro
> > Still not sure just what the heck it means. Is the taglib fucked up, or
> > is our expression evaluator too slow, or what? Or is it simply the case
> > that Velocity is pretty darn snappy.
>
> Velocity is pretty darn snappy. And I am incredibly biased towards this
> conclusion, so take it with a huge grain of salt :)
Highly biased opinion thus ignored ;-)
> > Any ideas, comments, thoughts?
>
> I see you got the #macro() trick to work. What was wrong?
Don't know really. The usual editing-until-it-works approach. At least
it works now :-)
/Rickard
--
Rickard Öberg
Software Development Specialist
xlurc - Xpedio Linköping Ubiquitous Research Center
Author of "Mastering RMI"
Email: rickard@xpedio.com
Re: [Webwork-user] Re: Velocity and WebWork: speed speed and more speed
Posted by Rickard Öberg <ri...@xpedio.com>.
Hey
Keng Wong wrote:
> I found a similar response with Netscape when using Freemarker as well. It seems like Netscape
> buffers the entire output prior to dumping it on screen/browser.
This makes no difference though as it is just rendering time we are
talking about, i.e. the rendering of the page at the serverside.
/Rickard
--
Rickard Öberg
Software Development Specialist
xlurc - Xpedio Linköping Ubiquitous Research Center
Author of "Mastering RMI"
Email: rickard@xpedio.com
Re: [Webwork-user] Re: Velocity and WebWork: speed speed and more speed
Posted by Rickard Öberg <ri...@xpedio.com>.
Attila Szegedi wrote:
> Does Netscape runs on the same machine as the server? I have noticed that
> while Netscape (4.72 on Windows) waits for a response, it hogs the CPU. So
> when I test a webapp with Netscape on the same machine that runs the server,
> I set Netscape process priority to "low".
Yup, that was the problem. So, from now on I only use IE5 to do these
tests.
/Rickard
>
> Attila.
>
> >
> > > -----Original Message-----
> > > From: Rickard Öberg [mailto:rickard@xpedio.com]
> > > Sent: Tuesday, August 07, 2001 7:35 AM
> > > To: webwork-user@lists.sourceforge.net
> > > Cc: velocity-user@jakarta.apache.org
> > > Subject: Re: [Webwork-user] Re: Velocity and WebWork: speed speed and
> > > more speed
> > >
> > >
> > > One weird thing though:
> > > The timings are all taken using a little WebWork action that internally
> > > uses URLConnection to get the data. This is used so as to get proper
> > > statistics by doing 100 hits at a time. Here's the weird part: when I
> > > use IE5 I get the same results as the test program, but using Netscape
> > > 4.7 I get about 90-110ms instead of 30-50ms. Might be something weird in
> > > how Netscape gets its data, but still...
> > >
> >
> >
--
Rickard Öberg
Software Development Specialist
xlurc - Xpedio Linköping Ubiquitous Research Center
Author of "Mastering RMI"
Email: rickard@xpedio.com
Re: [Webwork-user] Re: Velocity and WebWork: speed speed and more speed
Posted by Attila Szegedi <sz...@freemail.hu>.
Does Netscape runs on the same machine as the server? I have noticed that
while Netscape (4.72 on Windows) waits for a response, it hogs the CPU. So
when I test a webapp with Netscape on the same machine that runs the server,
I set Netscape process priority to "low".
Attila.
>
> > -----Original Message-----
> > From: Rickard Öberg [mailto:rickard@xpedio.com]
> > Sent: Tuesday, August 07, 2001 7:35 AM
> > To: webwork-user@lists.sourceforge.net
> > Cc: velocity-user@jakarta.apache.org
> > Subject: Re: [Webwork-user] Re: Velocity and WebWork: speed speed and
> > more speed
> >
> >
> > One weird thing though:
> > The timings are all taken using a little WebWork action that internally
> > uses URLConnection to get the data. This is used so as to get proper
> > statistics by doing 100 hits at a time. Here's the weird part: when I
> > use IE5 I get the same results as the test program, but using Netscape
> > 4.7 I get about 90-110ms instead of 30-50ms. Might be something weird in
> > how Netscape gets its data, but still...
> >
>
>
RE: [Webwork-user] Re: Velocity and WebWork: speed speed and more speed
Posted by Keng Wong <ke...@verizon.net>.
I found a similar response with Netscape when using Freemarker as well. It seems like Netscape
buffers the entire output prior to dumping it on screen/browser.
-keng wong
> -----Original Message-----
> From: Rickard Öberg [mailto:rickard@xpedio.com]
> Sent: Tuesday, August 07, 2001 7:35 AM
> To: webwork-user@lists.sourceforge.net
> Cc: velocity-user@jakarta.apache.org
> Subject: Re: [Webwork-user] Re: Velocity and WebWork: speed speed and
> more speed
>
>
> One weird thing though:
> The timings are all taken using a little WebWork action that internally
> uses URLConnection to get the data. This is used so as to get proper
> statistics by doing 100 hits at a time. Here's the weird part: when I
> use IE5 I get the same results as the test program, but using Netscape
> 4.7 I get about 90-110ms instead of 30-50ms. Might be something weird in
> how Netscape gets its data, but still...
>