Changes between Version 1 and Version 2 of SplittedCache


Ignore:
Timestamp:
2006-11-19T08:11:35+01:00 (7 years ago)
Author:
moo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SplittedCache

    v1 v2  
    1 = Splited Cache = 
    2 SplitedCache in XCache is designed for SMP servers. 
     1= Splitted Cache = 
     2SplittedCache in XCache is designed for SMP servers. 
    33 
    44By 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. 
    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 SplitedCache, 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 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. 
    88 
    99== How is it compares to non-blocking-reader == 
    10 SplitedCache and nonblocking reader give similar improvement on SMP, but: 
     10SplittedCache and nonblocking reader give similar improvement on SMP, but: 
    1111 1. nonblocking read way helps nothing for write 
    12  1. with SplitedCache 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 cpu need the same cache while the other cache is not needed 
    1313 
    1414(There isn't any tests to proven these words, correct me if i'm wrong)