Closed siyuanchai1999 closed 1 month ago
output is like this
Welcome to OSS version of cachebench
I0328 01:34:25.561690 40718 ReplayGeneratorBase.h:218] [0] Opened trace file reag0c01_20230315_20230322_0.2000.csv
Total 1.20M ops to be run
E0328 01:34:25.624919 40722 TimeStampTicker.cpp:57] A thread is trying to update too many buckets at one time: 0 to 2798105
E0328 01:34:25.624946 40724 TimeStampTicker.cpp:57] A thread is trying to update too many buckets at one time: 0 to 2798105
01:34:25 0.00M ops completed. Hit Ratio 0.00% (RAM 0.00%, NVM 0.00%)
== PieceWiseReplayGenerator Stats in Recent Time Window (1678863569 - 1678863601) ==
Total Processed Samples: 0.00 million
getBytes : 0.48 GB, getBytesPerSec : 0.00 GB/s, success : 4.01%, full success: 4.00%
getBodyBytes: 0.48 GB, getBodyBytesPerSec: 0.00 GB/s, success : 3.97%, full success: 3.97%
egressBytes : 0.48 GB, ingressBytes: 0.43 GB, egressBytesPerSec : 0.00 GB/s, ingressBytesPerSec: 0.00 GB/s, ingressEgressratio: 11.80%
objectGet : 706, objectGetPerSec : 1 /s, success : 37.11%, full success: 33.14%
== PieceWiseReplayGenerator Stats in Recent Time Window (1678863600 - 1678864202) ==
Total Processed Samples: 0.04 million
getBytes : 19.70 GB, getBytesPerSec : 0.03 GB/s, success : 22.67%, full success: 22.24%
getBodyBytes: 19.66 GB, getBodyBytesPerSec: 0.03 GB/s, success : 22.63%, full success: 22.22%
egressBytes : 19.68 GB, ingressBytes: 15.28 GB, egressBytesPerSec : 0.03 GB/s, ingressBytesPerSec: 0.03 GB/s, ingressEgressratio: 22.37%
objectGet : 36,940, objectGetPerSec : 61 /s, success : 51.39%, full success: 41.07%
I0328 01:34:26.649105 40718 PieceWiseReplayGenerator.cpp:271] Thread 15 finish, skip
01:35:25 0.79M ops completed. Hit Ratio 82.75% (RAM 82.75%, NVM 0.00%)
01:36:25 0.79M ops completed. Hit Ratio 0.00% (RAM 0.00%, NVM 0.00%)
01:37:25 0.79M ops completed. Hit Ratio 0.00% (RAM 0.00%, NVM 0.00%)
01:38:25 0.79M ops completed. Hit Ratio 0.00% (RAM 0.00%, NVM 0.00%)
01:39:25 0.79M ops completed. Hit Ratio 0.00% (RAM 0.00%, NVM 0.00%)
01:40:25 0.79M ops completed. Hit Ratio 0.00% (RAM 0.00%, NVM 0.00%)
01:41:25 0.79M ops completed. Hit Ratio 0.00% (RAM 0.00%, NVM 0.00%)
Hi, you can bypass this by changing "tickerSynchingSeconds" to 0 (or remove it from your cachebench config).
There is a known issue in ticker syncing that sometimes would cause the trace consumption to hang.
Hi, I ran cdn/202303/ trace according instruction here https://cachelib.org/docs/Cache_Library_User_Guides/Cachebench_FB_HW_eval/. The problem is that it seems never to finish even though I changed the config to
"numOps": 50000
. Is this expected behavior? IThe command I used is
Here's my config.