jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Smuts <asm...@yahoo.com>
Subject Re: Cache for large data that is crashing JVM
Date Wed, 14 Oct 2009 20:10:03 GMT
It can be configured to do all three and more.

The memory auxiliaries store data in memory.  

The indexed disk cache stores the data on disk and the keys in memory.  (There are other disk
caches as well.)  

If you use the JDBC disk cache, you can have JCS act as a facade on top of a database, such
as MySQL.  That way, no data would have to live in the local JVM.

What it sounds like you need is the remote cache.  You can start a JCS remote cache server.
 You can talk to it via rmi or you can run an http remote server (a servlet in the servlet
engine of your choice.)  I recommend the RMI remote cache.  You can have JCS keep some data
on the client side, the most active data.  Surely, not all million records are access as frequently.
. . . .  

Read the docs and experiment.  Ask away if you have any specific questions after consulting
the documentation.  


--- On Wed, 10/14/09, Armour, David L - DOT <David.Armour@dot.wi.gov> wrote:

> From: Armour, David L - DOT <David.Armour@dot.wi.gov>
> Subject: Cache for large data that is crashing JVM
> To: "'jcs-users@jakarta.apache.org'" <jcs-users@jakarta.apache.org>
> Date: Wednesday, October 14, 2009, 12:56 PM
> Hi
> Currently, I am trying to fix an old application that is
> loading 500 MB of data into memory and crashing the
> JVM.  I am wondering two things:
> 1.      Does JCS put the cache data into
> memory?  If yes, then I am going to still have too much
> for the JVM.  Does it write it to disk and then only
> hold the keys in memory?  Unfortunately, there are over
> a million records in this set.
> 2.      Can JCS be setup to run in it's own
> memory space (JVM) and then use some connection mechanism
> from the original application to JCS (like a database
> connection of some sort)?  This way the application JVM
> is not overloaded and the cache JVM can be configured
> properly.
> Any other ideas or thoughts?
> Thanks.
> David Armour

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

View raw message