I know that. :)
The database was just upgraded and io/cpu is really really low. So that
won't be the case. The root cause might be the number of db requests
required to render a page, but the database it self is not the bottle
neck. :) :)
Thiago H. de Paula Figueiredo wrote:
Em Thu, 15 Jan 2009 20:57:19 -0300, Fernando Padilla <f...@alum.mit.edu>
escreveu:
Well, we have a large app that is not performing very well.. and now I
have to figure out how to make it more performant..
In my humble opinion, you're starting to performance bottleneck from the
wrong side of the stack. Most of the time, the culprit is the database
(or any other data storage implementation). I would start by logging the
running time of the data access methods.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
