On 2018-04-16 18:16, Mark Vitale wrote:
[...]
You may find the following commands useful when tuning the cache:

cmdebug <client> -cache           # gives the current cache configuration

xstat_cm_test <client> 2 -onceonly | head -n 35           # gives live cache 
statistics

Mark,

Thanks a lot for clearing this up, you really put me on track.

One more thing however, before I have a go at the cm configuration: regarding xstat_cm_test, what are {d,v}{local,remote}Accesses ? Do they correlate with cache hits somehow so one can infer the cache misses? For reference, here's what xstat_cm_test tells me:

Overall Performance Info:
-------------------------
             6 numPerfCalls
    1523004872 epoch
             1 numCellsVisible
             1 numCellsContacted
    1414893978 dlocalAccesses
     790563320 vlocalAccesses
        566088 dremoteAccesses
          3105 vremoteAccesses
         31250 cacheNumEntries
       1000000 cacheBlocksTotal
        536319 cacheBlocksInUse
       1000000 cacheBlocksOrig
           650 cacheMaxDirtyChunks
             0 cacheCurrDirtyChunks
    1415304535 dcacheHits
     790375884 vcacheHits

Thanks again,

-Kostas.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to