You can still do diffs from one Cayenne version to another. I just want
to eliminate things like Jetty/Tomcat performance (they do differ in
startup times/etc) and only focus on Cayenne. Also, it would be much
simpler to run if Cayenne-only. Wouldn't force someone to install a
bunch of extra software that arguably doesn't give them anything, except
a bigger footprint on the HD. The more layers you add, the harder it is
to setup and maintain.
I've not looked at JMeter, but perhaps I can take a peek at it later if
I have time.
Thanks!
/dev/mrg
-----Original Message-----
From: news [mailto:new..ea.gmane.org] On Behalf Of Ahmed Mohombe
Sent: Wednesday, February 01, 2006 9:44 AM
To: cayenne-deve..bjectstyle.org
Subject: Re: Cayenne performance testing
> I kind of disagree about the web application testing part. I think if
> we are going to profile code, it should be Cayenne code. Let the
> Tapestry/Struts/JSP/JSF/Tomcat/Jetty/Resin/WebSphere/JBoss/etc guys
> worry about profiling their code.
As Andrus said, it's not about the raw performance, but about the "Diff"
from
one version to the other of Cayenne. In this case, since the
webapplication on
top of Cayenne remains the same, the diff would represent the pure
cayenne numbers.
Considering how simple is to do this with JMeter, IMHO it represents the
smallest
possible effort with the greatest results. Not to mention about the nice
diagrams
and statistics JMeter offers, all this for free, with the lease possible
work.
just my 2 cents,
Ahmed.
This archive was generated by hypermail 2.0.0 : Wed Feb 01 2006 - 09:51:01 EST