Changes between Version 2 and Version 3 of SplittedCache


Ignore:
Timestamp:
2006-11-20T04:44:47+01:00 (8 years ago)
Author:
chrisbolt
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SplittedCache

    v2 v3  
    22SplittedCache in XCache is designed for SMP servers. 
    33 
    4 By setting xcache.count or xcache.var_count to 2 or more to take the advantage. The recommended value to use is count of your cpu + 1, but u can always try to tune it yourself like other settings. 
     4By setting xcache.count or xcache.var_count to 2 or more to take the advantage. The recommended value to use is count of your cpu + 1, but you can always try to tune it yourself like other settings. 
    55 
    66== How it works == 
    7 On SMP servers, CPUs can access memory parallelly, while the XCache shared memory have to be accessed. By enabling SplittedCache, XCache will split the cache by xcache.count (or xcache.var_count), so both of them can be accessed at the same time. 
     7On SMP servers, CPUs can access memory in parallel, while the XCache shared memory have to be accessed. By enabling SplittedCache, XCache will split the cache by xcache.count (or xcache.var_count), so both of them can be accessed at the same time. 
    88 
    99== How is it compares to non-blocking-reader == 
    1010SplittedCache and nonblocking reader give similar improvement on SMP, but: 
    1111 1. nonblocking read way helps nothing for write 
    12  1. with SplittedCache it is possible that 2 cpu need the same cache while the other cache is not needed 
     12 1. with SplittedCache it is possible that 2 CPUs need the same cache while the other cache is not needed 
    1313 
    14 (There isn't any tests to proven these words, correct me if i'm wrong) 
     14(There aren't any tests to prove these words, correct me if I'm wrong)