tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Guyatt" <pguy...@telesoft-technologies.com>
Subject RE: Accessing objects with any servlets, where the object is already pre-created
Date Tue, 07 Oct 2003 11:50:47 GMT
Hi there,

I beleive that using the setAttribute adds the object to a hashtable.

If when the hashtable reaches a certian limit (usually 75% of its total
size) it re-hashs which can be expensive and cause performance problems. The
solution is to ensure that the limit is never reached. Is there a way to set
the initial limit for the context?

Pete

-----Original Message-----
From: Tim Funk [mailto:funkman@joedog.org]
Sent: 07 October 2003 12:33
To: Tomcat Users List
Subject: Re: Accessing objects with any servlets, where the object is
already pre-created


I can't see why there would be a difference.

-Tim

Vidar Langberget wrote:

> Have you noticed any performance problems with storing large amounts of
data
> in the servlet context?
>
> I'm developing a cache for my webapp, and I can't decide if I want to use
a
> static class or store cache instances in the servlet context.
>
>
> Vidar
>
> ----- Original Message -----
> From: "Tim Funk" <funkman@joedog.org>
>
>
>>My preference is to store the data into the servlet context (using
>>setAttribute). Then no static variables are needed.
>


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


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


Mime
View raw message