Christopher,
I think you should just start by measuring different layers of your
application and different pathes the use cases go, and then start to
think how to improve things that are slow.
Blind performance tuning without knowing where the problem lies is the
last thing that will help you.
I'd second that book recommendation. I've read it and there's a lot of
good tips in there.
On 3/22/07, Karr, David [EMAIL PROTECTED] wrote:
One I like is Pro Java EE 5 Performance Management and Optimization,
by Steven Haines. Note that Steven Haines is associated with Quest
Software and
To: Struts Users Mailing List
Subject: Re: Book recommendations for performance tuning
I'd second that book recommendation. I've read it and there's a lot of
good tips in there.
On 3/22/07, Karr, David [EMAIL PROTECTED] wrote:
One I like is Pro Java EE 5 Performance Management and Optimization
Chris,
I think before going for performance tuning you would have to decide on two
things- A Load Generator and a Performance Profiler. Then you generate load and
profile the application to find out exactly which layer\section of code\network
needs to be tuned\upgraded. Then you focus on tuning
work with them.
Thanks, Chris
-Original Message-
From: Asthana, Rahul [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 5:30 PM
To: Struts Users Mailing List
Subject: RE: Book recommendations for performance tuning
Chris,
I think before going for performance tuning you would have
One I like is Pro Java EE 5 Performance Management and Optimization,
by Steven Haines. Note that Steven Haines is associated with Quest
Software and Jprobe (and related products). Although the book uses some
pictures from those products, it is not in any way a veiled ad for
those products. In
6 matches
Mail list logo