I sometimes get 0 Ops/sec in memtiers json output if run against memcached. Here is the setup: I have 3 client VMs on Azure, each running a single instance of memtier version 1.2.14. Then I have a single server VM on Azure running an instance of memcached version 1.5.6. I start each memtier instance with the following options: --server=<ip_of_memcached_vm> --port=<port_of_memcached_vm> --protocol=memcache_text --ratio=1:0 --expiry-range=9999-10000 --key-maximum=10000 --hide-histogram --clients=56 --threads=2 --test-time=75 --data-size=4096 --json-out-file=client.json &> mt1.txt
memcached is started like this: memcached -p <port_of_server> -t 1 -v &> mc1.log It happens that often (not always) at least one memtier client ouputs a json with 0 Ops/sec. In this case, the corresponding mt1.txt (where stdout & stderr are redirected to) shows the error message "read error: connection reset by peer". I have no idea why this happens and would appreciate your help. -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
