Dear Jim,
Thanks for your answer.
The OS' file-system cache acts as a storage server cache. The storage
server does (essentially) no processing to data read from disk, so an
application-level cache would add nothing over the disk cache provided by
the storage server.
I see, then I guess it
On 13 February 2012 10:06, Pedro Ferreira jose.pedro.ferre...@cern.ch wrote:
The OS' file-system cache acts as a storage server cache. The storage
server does (essentially) no processing to data read from disk, so an
application-level cache would add nothing over the disk cache provided by
between processes, which doesn't make them very useful , in which we
very useful *for our setup*
--
José Pedro Ferreira
Software Developer, Indico Project
http://indico-software.org
+---+
+ '``'--- `+ CERN - European Organization for Nuclear Research
+ |CERN| / + 1211 Geneve
On Mon, Feb 13, 2012 at 5:06 AM, Pedro Ferreira
jose.pedro.ferre...@cern.ch wrote:
Dear Jim,
Thanks for your answer.
The OS' file-system cache acts as a storage server cache. The storage
server does (essentially) no processing to data read from disk, so an
application-level cache would
Having enough ram to hold your entire database may not be practical.
Ideally, you want enough to hold the working set. For many applications,
most of the database reads are from the later part of the file. The working
set is often much smaller than the whole file.
That is a very good point. I
Hello all,
A (possibly silly) question: does ZEO have some kind of server-side
cache? I mean, each time an oid is requested by one of the clients is it
retrieved from the DB file directly, or are some of the objects kept in
memory? From what I see in the code, the latter doesn't seem to
On Fri, Feb 10, 2012 at 4:49 AM, Pedro Ferreira
jose.pedro.ferre...@cern.ch wrote:
Hello all,
A (possibly silly) question: does ZEO have some kind of server-side cache? I
mean, each time an oid is requested by one of the clients is it retrieved
from the DB file directly, or are some of the
