Thank you all for the answers and please apologize my late answer, my
family obligated me to a 10 day vacation without internet...
I added Franks recommendation (mainly because it was the first to come
:-)) to my recommendations to the client, and we both thought them
reasonable... However, now he
there's plenty of papers on the topic on the internet, including the
ones listed on tomcat's website.
have you looked at the resource page?
http://tomcat.apache.org/resources.html
On Thu, Jul 3, 2008 at 9:05 AM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
> there is one criteria that I al
there is one criteria that I always use, and that is "user response time"
this can work for almost any webapp that has some sort of "real" user in
front of it.
50 to 100ms would be excellent and very aggressive, but it depends on
the app itself of course.
2-3 seconds for a complete page load is
It might be a little simplistic, but we've always used a simple "100
user" metric: if we can simulate 100 simultaneous users on a site, or
webapp (in the sense of RIAs) and all the responses across the app come
back in reasonable times (which you can define variably as you see fit),
then we gen
Hi all,
recently I was asked by someone to define performance requirements for
a site without even knowing it (the site).
The task was to deliver standard requirements valid for most sites (or
portal-like sites).
I answered that it's probably impossible without knowing the type of
media delivered,
