You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Jon Stevens <jo...@latchkey.com> on 2001/12/02 21:07:14 UTC

Re: caching OM objetcs

on 11/30/01 9:45 AM, "Colin Chalmers" <co...@xs4all.nl> wrote:

> Hi,
> 
> Is there are *recommended* way of caching OM objects or should I utilise the
> Pool and/or global cache (service)?
> 
> I've got a number of classes that seem to be accessing the same data
> increasing db calls unecessarily
> 
> Thx
> 
> /Colin
> 

We haven't come up with a good solution yet. There are a lot of issues
surrounding expiration of those objects because of the relational nature of
all of them.

-jon


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: caching OM objetcs

Posted by Daniel Rall <dl...@collab.net>.
On Sun, 2 Dec 2001, Jon Stevens wrote:

> on 12/2/01 12:14 PM, "Jason van Zyl" <jv...@zenplex.com> wrote:
>
> > I believe that Aaron Smut's caching code will go a long way toward
> > implementing something that will work for Torque.
>
> I fully second that and that is the direction that I would take when I am
> ready to look into it. Scarab *really* needs to have the objects cached.
>
> Right now, performance on some of the database heavy screens (ie: ViewIssue)
> isn't as good as I would like it to be and adding minimal caching has shown
> to increase the speed and exceptional amount.

SourceCast had to have caching to scale.



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: caching OM objetcs

Posted by Jon Stevens <jo...@latchkey.com>.
on 12/2/01 12:14 PM, "Jason van Zyl" <jv...@zenplex.com> wrote:

> I believe that Aaron Smut's caching code will go a long way toward
> implementing something that will work for Torque.

I fully second that and that is the direction that I would take when I am
ready to look into it. Scarab *really* needs to have the objects cached.

Right now, performance on some of the database heavy screens (ie: ViewIssue)
isn't as good as I would like it to be and adding minimal caching has shown
to increase the speed and exceptional amount.

-jon


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: caching OM objetcs

Posted by Jason van Zyl <jv...@zenplex.com>.
On 12/2/01 3:07 PM, "Jon Stevens" <jo...@latchkey.com> wrote:

> on 11/30/01 9:45 AM, "Colin Chalmers" <co...@xs4all.nl> wrote:
> 
>> Hi,
>> 
>> Is there are *recommended* way of caching OM objects or should I utilise the
>> Pool and/or global cache (service)?
>> 
>> I've got a number of classes that seem to be accessing the same data
>> increasing db calls unecessarily
>> 
>> Thx
>> 
>> /Colin
>> 
> 
> We haven't come up with a good solution yet. There are a lot of issues
> surrounding expiration of those objects because of the relational nature of
> all of them.

I believe that Aaron Smut's caching code will go a long way toward
implementing something that will work for Torque.
 
> -jon
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>

-- 

jvz.

Jason van Zyl

http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>