Commit 052d462e authored by Jeremy Hylton's avatar Jeremy Hylton

Revise explanation of cache now that ZEO 2.0 is out.

parent bba39751
...@@ -35,17 +35,15 @@ ZEO Client Cache ...@@ -35,17 +35,15 @@ ZEO Client Cache
transactions commit locally, or as data are loaded from the transactions commit locally, or as data are loaded from the
server. server.
- When a cache hit is found in the old cache file, it is copied to
the current cache file.
- When the current cache file size exceeds one half the cache size, the - When the current cache file size exceeds one half the cache size, the
first cache file is recreated and designated the "current" cache first cache file is recreated and designated the "current" cache
file. The second cache file becomes the "old" cache file. file. The second cache file becomes the "old" cache file.
and so on. and so on.
As of ZEO 2.0 beta 2, the above algorithm is augmented as follows.
When a cache load finds a hit in the "old" cache file, the data is
copied to the "current" cache file. This appears to improve the hit
rate.
Persistent cache files are created in the directory named in the Persistent cache files are created in the directory named in the
'var' argument to the ClientStorage (see ClientStorage.txt) or in 'var' argument to the ClientStorage (see ClientStorage.txt) or in
the 'var' subdirectory of the directory given by the INSTANCE_HOME the 'var' subdirectory of the directory given by the INSTANCE_HOME
...@@ -66,3 +64,4 @@ ZEO Client Cache ...@@ -66,3 +64,4 @@ ZEO Client Cache
For example, the second cache file for storage 'spam' and client 8881 For example, the second cache file for storage 'spam' and client 8881
would be named 'cspam-8881-1.zec'. would be named 'cspam-8881-1.zec'.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment