[jdjlist] RE: Caching

[Greg Nudelman]

James, it sounds like the between-machines global cache manager servlet just gathers the data?  In other words, if you have 4 machines you do not store 25% of the total cache on each, but instead you store 100% of the cache on each machine independently. If you add 3 more machines, you'll have to store 3 more 100% copies of the cache...   If so, that is exactly what we do as well, but this is far from ideal for our business model. We use the parameter cache for pricing, and any of the pricing parameters can expire at any time, but that frequency depends on the type of the parameter.  The total number of the parameters is huge, and it can not be loaded into the cache all at once.    I was hoping to find something that will allow me to have a distributed cache, so that by adding more machines, I can proportionally scale the cache capacity.   Sounds like a challenge, right?   :-(   Greg     -----Original Message----- From: James Stauffer [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 1:05 PM To: jdjlist Subject: [jdjlist] RE: Caching We don't cache data that changes much so we don't have to worry about expired data.  We allow duplicates so that each machine is completely independent (except for the Database).   James Stauffer --- You are currently subscribed to jdjlist as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] http://www.sys-con.com/fusetalk