Thanks for the prompt replies. If it makes you feel better, the paper has
stopped existing in my mind. :)
Have a good weekend!
On Friday, March 26, 2021 at 5:44:29 PM UTC-7 Dormando wrote:
> Hey,
>
> > This worked! However it seems like TCP and UDP latency now is about the
> same with my code
Hey,
> This worked! However it seems like TCP and UDP latency now is about the same
> with my code as well as with a real
> benchmarking tool (memaslap).
I don't use memaslap so I can't speak to it. I use mc-crusher for the
"official" testing, though admittedly it's harder to configure.
> Not
Thanks for the reply! responses inline
On Friday, March 26, 2021 at 2:03:10 PM UTC-7 Dormando wrote:
> Hey,
>
> Usually it's good to include the benchark code, but I think I can answer
> this off the top of my head:
>
> 1) set at least 1,000 keys and fetch them randomly. all of memcached's
>
Hey,
Usually it's good to include the benchark code, but I think I can answer
this off the top of my head:
1) set at least 1,000 keys and fetch them randomly. all of memcached's
internal scale-up is based around... not just fetching a single key. I
typically test with a million or more. There
We are trying to experiment with using UDP vs TCP for gets to see what kind
of speedup we can achieve. I wrote a very simple benchmark that just uses a
single thread to set a key once and do gets to retrieve the key over and
over. We didn't notice any speedup using UDP. If anything we saw a
