Non-replicated YCSB performance and caching.  
We first evaluate the performance of running YCSB without replication using one client server and one Clio memory device.
Figure REF  and REF  plot the average end-to-end latency and throughput of running the YCSB workloads with (1) the original Clio, (2) Clio's Go-Back-N transport offloaded to sNIC (Clio-sNIC), (3) adding caching on top of Clio-sNIC (Clio-sNIC-$), (4) Clover [1]}, a passive disaggregated memory system where all processing happens at the client side and a global metadata server, (5) HERD [2]}, a two-sided RDMA system where both the client and memory sides are regular servers, and (6) HERD running on the NVidia BlueField SmartNIC [3]} (HERD-BF).
sNIC's performance is on par with Clio, Clover, and HERD, as it only adds a small overhead to the baseline Clio.
With caching NT, sNIC achieves the best performance among all systems, esp. on throughput.
This is because all links in our testbed are 100 Gbps except for the link to the 10 Gbps Clio boards. When there is a cache hit at the sNIC, we avoid going to the 10 Gbps Clio boards.
HERD-BF performs the worst because of the slow link between its NIC and the ARM processor.
