jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Smuts <aasm...@wisc.edu>
Subject RE: Spooling after each update
Date Thu, 05 Jun 2003 12:39:14 GMT
All you'd need to do is create a disk auxiliary and give it type lateral
and then turn spooling off.  Type lateral auxiliaries are given every
element on put.  Type disk are overflow auxiliaries.  

How did you modify the disk cache to recover from a crash?

Aaron

> -----Original Message-----
> From: Vossberg, Michal [mailto:Michal.Vossberg@jamba-ag.de]
> Sent: Wednesday, June 04, 2003 9:56 AM
> To: 'Turbine JCS Users List'
> Subject: AW: Spooling after each update
> 
> Aaron,
> thanks, but maybe I didn't make myself clear: I still want to use a
> decently
> sized memory cache, the disk cache is auxiliary. I guess your solution
> wouldn't help then.
> Michal
> 
> 
> 
> > -----Ursprungliche Nachricht-----
> > Von: Aaron Smuts [mailto:aasmuts@wisc.edu]
> > Gesendet: Mittwoch, 4. Juni 2003 16:37
> > An: 'Turbine JCS Users List'
> > Betreff: FW: Spooling after each update
> >
> >
> >
> > You could just set the memory size to some very small number like 1.
> > This way everything will go right to disk.
> >
> > > -----Original Message-----
> > > From: Vossberg, Michal [mailto:Michal.Vossberg@jamba-ag.de]
> > > Sent: Wednesday, June 04, 2003 6:49 AM
> > > To: 'turbine-jcs-user@jakarta.apache.org'
> > > Subject: Spooling after each update
> > >
> > > Hi,
> > > we are implementing an auxiliary disk cache plugin that better
suits
> > out
> > > needs.
> > > For this, I want each element explicitly put to disk with the
update
> > of
> > > the
> > > memory cache, not only spool them lru after reaching the limit.
> > > I added the spooling to the aux-update part of the CompositeCache
> > update
> > > method
> > > which works fine but I wonder if that's the best (and
> > intended) place.
> > Any
> > > other
> > > idea without intruding the core?
> > > Also, doing this the spooling of the memory manager becomes
somewhat
> > > redundant. What's the best way to turn it off but still
> > keep the limit
> > of
> > > the memory cache.
> > > I don't see that setting the element attributes to
> > isSpool=false will
> > help
> > > as it's
> > > not being checked in the spooling method (and in fact it
doesn't)!?
> > > Any advice will be greatly appreciated,
> > > Thanks
> > > Michal
> > >
> > > --- Michal Vossberg
> > > Development Mobile Applications
> > > Jamba! AG - Pfuelstrasse 5 - 10997 Berlin
> > > Phone: +49-30-69538-176
> > > Fax: +49-30-69538-599
> > > Web: http://www.jamba.de
> > > WAP: http://wap.jamba.de/
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > turbine-jcs-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> > turbine-jcs-user-help@jakarta.apache.org
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > turbine-jcs-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> > turbine-jcs-user-help@jakarta.apache.org
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
turbine-jcs-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-jcs-user-help@jakarta.apache.org


Mime
View raw message