Re: Is ARM64 officially supported ?
If you're still stuck I'll write more of a guide, just let me know. On Sun, 22 Mar 2020, dormando wrote: > Hey, > > I thought I wrote this in the rest of the e-mail + the README: it doesn't > print stats at the end. you run the benchmark and then pull stats via > other utilities. Take a close look at what I wrote and the files in the > repo. > > On Sun, 22 Mar 2020, Martin Grigorov wrote: > > > Hi, > > > > On Thu, Mar 19, 2020 at 9:06 PM dormando wrote: > > memtier is trash. Check the README for mc-crusher, I just updated it > > a bit > > a day or two ago. Those numbers are incredibly low, I'd have to dig a > > laptop out of the 90's to get something to perform that badly. > > > > mc-crusher runs blindly and you use the other utilities that come > > with it > > to find command rates and sample the latency while the benchmark runs. > > Almost all 3rd party memcached benchmarks end up benchmarking the > > benchmark tool, not the server. I know mc-crusher doesn't make it very > > obvious how to use though, sorry. > > > > > > What I miss to find so far is how to get the statistics after a run. > > For example, I run > > ./mc-crusher --conf ./conf/asciiconf --ip 192.168.1.43 --port 12345 > > --timeout 10 > > > > and the output is: > > > > -- > > ip address default: 192.168.1.43 > > port default: 12345 > > id 0 for key send value ascii_get > > id 1 for key recv value blind_read > > id 5 for key conns value 50 > > id 8 for key key_prefix value foobar > > id 26 for key key_prealloc value 0 > > id 24 for key pipelines value 8 > > id 0 for key send value ascii_set > > id 1 for key recv value blind_read > > id 5 for key conns value 10 > > id 8 for key key_prefix value foobar > > id 26 for key key_prealloc value 0 > > id 24 for key pipelines value 4 > > id 19 for key stop_after value 20 > > id 3 for key usleep value 1000 > > id 12 for key value_size value 10 > > setting a timeout > > done initializing > > timed run complete > > -- > > > > And I see that the server is busy at that time. > > How to find out how many sets/gets/... were made ? > > > > Martin > > > > > > A really quick untuned test against my raspberry pi 3 nets 92,000 > > gets/sec. (mc-crusher running on a different machine). On a xeon > > machine > > I can get tens of millions of ops/sec depending on the read/write > > ratio. > > > > On Thu, 19 Mar 2020, Martin Grigorov wrote: > > > > > Hi > > > > > > I've made some local performance testing > > > > > > First I tried with https://github.com/memcached/mc-crusher but it > > seems it doesn't calculate any statistics after the load runs. > > > > > > The results below are from > > https://github.com/RedisLabs/memtier_benchmark > > > > > > 1) Text > > > ./memtier_benchmark --server XYZ --port 12345 -P memcache_text > > > > > > ARM64 text > > > > > = > > > Type Ops/sec Hits/sec Misses/sec Latency > > KB/sec > > > > > - > > > Sets 985.28 --- --- 20.02700 > > 67.22 > > > Gets 9842.00 0.00 9842.00 20.01900 > > 248.83 > > > Waits 0.00 --- --- 0.0 > > --- > > > Totals 10827.28 0.00 9842.00 20.02000 > > 316.05 > > > > > > > > > X86 text > > > > > = > > > Type Ops/sec Hits/sec Misses/sec Latency > > KB/sec > > > > > - > > > Sets 931.04 --- --- 20.06800 > > 63.52 > > > Gets 9300.21 0.00 9300.21 20.32600 > > 235.13 > > > Waits 0.00 --- --- 0.0 > > --- > > > Totals 10231.26 0.00 9300.21 20.30200 > > 298.66 > > > > > > > > > > > > 2) Binary > > > ./memtier_benchmark --server XYZ --port 12345 -P memcache_binary > > > > > > ARM64 binary > > > > > = > > > Type Ops/sec Hits/sec Misses/sec Latency > > KB/sec > > > > > - > > > Sets 829.68 --- --- 23.46500 > > 63.90 > > > Gets 8287.69 0.00 8287.69 23.56100 > >
Re: Is ARM64 officially supported ?
Hey, I thought I wrote this in the rest of the e-mail + the README: it doesn't print stats at the end. you run the benchmark and then pull stats via other utilities. Take a close look at what I wrote and the files in the repo. On Sun, 22 Mar 2020, Martin Grigorov wrote: > Hi, > > On Thu, Mar 19, 2020 at 9:06 PM dormando wrote: > memtier is trash. Check the README for mc-crusher, I just updated it a > bit > a day or two ago. Those numbers are incredibly low, I'd have to dig a > laptop out of the 90's to get something to perform that badly. > > mc-crusher runs blindly and you use the other utilities that come with > it > to find command rates and sample the latency while the benchmark runs. > Almost all 3rd party memcached benchmarks end up benchmarking the > benchmark tool, not the server. I know mc-crusher doesn't make it very > obvious how to use though, sorry. > > > What I miss to find so far is how to get the statistics after a run. > For example, I run > ./mc-crusher --conf ./conf/asciiconf --ip 192.168.1.43 --port 12345 --timeout > 10 > > and the output is: > > -- > ip address default: 192.168.1.43 > port default: 12345 > id 0 for key send value ascii_get > id 1 for key recv value blind_read > id 5 for key conns value 50 > id 8 for key key_prefix value foobar > id 26 for key key_prealloc value 0 > id 24 for key pipelines value 8 > id 0 for key send value ascii_set > id 1 for key recv value blind_read > id 5 for key conns value 10 > id 8 for key key_prefix value foobar > id 26 for key key_prealloc value 0 > id 24 for key pipelines value 4 > id 19 for key stop_after value 20 > id 3 for key usleep value 1000 > id 12 for key value_size value 10 > setting a timeout > done initializing > timed run complete > -- > > And I see that the server is busy at that time. > How to find out how many sets/gets/... were made ? > > Martin > > > A really quick untuned test against my raspberry pi 3 nets 92,000 > gets/sec. (mc-crusher running on a different machine). On a xeon machine > I can get tens of millions of ops/sec depending on the read/write ratio. > > On Thu, 19 Mar 2020, Martin Grigorov wrote: > > > Hi > > > > I've made some local performance testing > > > > First I tried with https://github.com/memcached/mc-crusher but it > seems it doesn't calculate any statistics after the load runs. > > > > The results below are from > https://github.com/RedisLabs/memtier_benchmark > > > > 1) Text > > ./memtier_benchmark --server XYZ --port 12345 -P memcache_text > > > > ARM64 text > > > = > > Type Ops/sec Hits/sec Misses/sec Latency > KB/sec > > > - > > Sets 985.28 --- --- 20.02700 > 67.22 > > Gets 9842.00 0.00 9842.00 20.01900 > 248.83 > > Waits 0.00 --- --- 0.0 > --- > > Totals 10827.28 0.00 9842.00 20.02000 > 316.05 > > > > > > X86 text > > > = > > Type Ops/sec Hits/sec Misses/sec Latency > KB/sec > > > - > > Sets 931.04 --- --- 20.06800 > 63.52 > > Gets 9300.21 0.00 9300.21 20.32600 > 235.13 > > Waits 0.00 --- --- 0.0 > --- > > Totals 10231.26 0.00 9300.21 20.30200 > 298.66 > > > > > > > > 2) Binary > > ./memtier_benchmark --server XYZ --port 12345 -P memcache_binary > > > > ARM64 binary > > > = > > Type Ops/sec Hits/sec Misses/sec Latency > KB/sec > > > - > > Sets 829.68 --- --- 23.46500 > 63.90 > > Gets 8287.69 0.00 8287.69 23.56100 > 314.75 > > Waits 0.00 --- --- 0.0 > --- > > Totals 9117.37 0.00 8287.69 23.55200 > 378.65 > > > > X86 binary > > > = > > Type Ops/sec Hits/sec Misses/sec Latency >
Re: Is ARM64 officially supported ?
Hi, On Thu, Mar 19, 2020 at 9:06 PM dormando wrote: > memtier is trash. Check the README for mc-crusher, I just updated it a bit > a day or two ago. Those numbers are incredibly low, I'd have to dig a > laptop out of the 90's to get something to perform that badly. > > mc-crusher runs blindly and you use the other utilities that come with it > to find command rates and sample the latency while the benchmark runs. > Almost all 3rd party memcached benchmarks end up benchmarking the > benchmark tool, not the server. I know mc-crusher doesn't make it very > obvious how to use though, sorry. > What I miss to find so far is how to get the statistics after a run. For example, I run ./mc-crusher --conf ./conf/asciiconf --ip 192.168.1.43 --port 12345 --timeout 10 and the output is: -- ip address default: 192.168.1.43 port default: 12345 id 0 for key send value ascii_get id 1 for key recv value blind_read id 5 for key conns value 50 id 8 for key key_prefix value foobar id 26 for key key_prealloc value 0 id 24 for key pipelines value 8 id 0 for key send value ascii_set id 1 for key recv value blind_read id 5 for key conns value 10 id 8 for key key_prefix value foobar id 26 for key key_prealloc value 0 id 24 for key pipelines value 4 id 19 for key stop_after value 20 id 3 for key usleep value 1000 id 12 for key value_size value 10 setting a timeout done initializing timed run complete -- And I see that the server is busy at that time. How to find out how many sets/gets/... were made ? Martin > > A really quick untuned test against my raspberry pi 3 nets 92,000 > gets/sec. (mc-crusher running on a different machine). On a xeon machine > I can get tens of millions of ops/sec depending on the read/write ratio. > > On Thu, 19 Mar 2020, Martin Grigorov wrote: > > > Hi > > > > I've made some local performance testing > > > > First I tried with https://github.com/memcached/mc-crusher but it seems > it doesn't calculate any statistics after the load runs. > > > > The results below are from > https://github.com/RedisLabs/memtier_benchmark > > > > 1) Text > > ./memtier_benchmark --server XYZ --port 12345 -P memcache_text > > > > ARM64 text > > = > > Type Ops/sec Hits/sec Misses/sec Latency KB/sec > > - > > Sets 985.28 --- --- 20.0270067.22 > > Gets 9842.00 0.00 9842.00 20.01900 248.83 > > Waits 0.00 --- --- 0.0 --- > > Totals 10827.28 0.00 9842.00 20.02000 316.05 > > > > > > X86 text > > = > > Type Ops/sec Hits/sec Misses/sec Latency KB/sec > > - > > Sets 931.04 --- --- 20.0680063.52 > > Gets 9300.21 0.00 9300.21 20.32600 235.13 > > Waits 0.00 --- --- 0.0 --- > > Totals 10231.26 0.00 9300.21 20.30200 298.66 > > > > > > > > 2) Binary > > ./memtier_benchmark --server XYZ --port 12345 -P memcache_binary > > > > ARM64 binary > > = > > Type Ops/sec Hits/sec Misses/sec Latency KB/sec > > - > > Sets 829.68 --- --- 23.4650063.90 > > Gets 8287.69 0.00 8287.69 23.56100 314.75 > > Waits 0.00 --- --- 0.0 --- > > Totals 9117.37 0.00 8287.69 23.55200 378.65 > > > > X86 binary > > = > > Type Ops/sec Hits/sec Misses/sec Latency KB/sec > > - > > Sets 829.32 --- --- 23.6360063.87 > > Gets 8284.10 0.00 8284.10 23.58600 314.61 > > Waits 0.00 --- --- 0.0 --- > > Totals 9113.42 0.00 8284.10 23.59100 378.48 > > > > > > > > Text is faster on the ARM64. Binary is similar for both. > > > > The benchmarking tool runs on different machine than the ones running > Memcached: > > > > The ARM64 server has this spec: > > > > $ lscpu > > Architecture:aarch64 > > Byte Order: Little Endian > > CPU(s): 4 > > On-line CPU(s) list: 0-3 > > Thread(s) per core: 1 > > Core(s)
