Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of p@pidster.com designates
 87.106.82.221 as permitted sender)
Received-SPF: neutral (s15243851.onlinehome-server.info: 78.86.122.68 is
 neither permitted nor denied by domain of pidster.com)
 client-ip=78.86.122.68; envelope-from=p@pidster.com; helo=Phoenix.config;
Message-ID: <4A24E4C8.5060807@pidster.com>
Date: Tue, 02 Jun 2009 09:37:28 +0100
From: Pid <p@pidster.com>
Reply-To: p@pidster.com
Organization: Pid Inc
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Caching rendered page - reducing hits to the backend?
References: <BLU0-SMTP23D89CB4FBF2A94DBD89E1C54E0@phx.gbl>
 <8178667D-4429-469C-9901-CC368127DE70@gmail.com>
In-Reply-To: <8178667D-4429-469C-9901-CC368127DE70@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Have you already measured the performance of your application and
determined that caching the rendered pages is the appropriate thing to
do - ie how have you determined that database access is the bottleneck?

If not, caching page content may just hide a multitude of performance
related sins.

JPA's built-in caching may already provide enough in the way of
performance improvements to make an additional caching layer pointless.

Is the database on a different machine or the same one and are you
clustering Tomcat?

You're probably worrying unnecessarily.

p


Markus Stauffer wrote:
> like this: http://www.opensymphony.com/oscache/  ?
> 
> 
> Am 30.05.2009 um 21:51 schrieb Andre-John Mas:
> 
>> Hi,
>>
>> Much of the content on the site which I am in the process will be
>> semi-static, and I want to be able to cache the rendered pages to
>> reduce database hits. To explain:
>>
>> A given page will depend on dynamic data that is stored in the
>> database, but that data is updated about once a month. The only true
>> dynamic information will be the header where the user login state is
>> shown. There will likely be a few million entries in this database and
>> we are planning to support high traffic. The pages can be localised.
>> The page is going to be queried as such:
>>
>>  http://myhost.com/myapp.action?id=12345678
>>
>> Although I am using a direct JPA access, we might change to use web
>> services in the future.
>>
>> Am I worrying unecessarily? At the same time are there recommended
>> approaches. I am currently using struts2 and JPA for the web site, if
>> it makes a difference.
>>
>> Andr�-John
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org