I don't really have high visibility into the average item size but I see what you mean.
Stats should give us good info on that right? On Aug 27, 2016 1:46 AM, "dormando" <[email protected]> wrote: > > > > Thank you for the tips guys! > > > > The limiting factor for us is actually memory utilization. We are using > the default configuration on sizable ec2 nodes and pulling only like 20k > qps per node. Which is fine > > because we need to shard the key set over x servers to handle the mem > req (30G) per server. > > > > I should have looked into that before posting. > > > > I am really curious about network saturation though. 200k gets at 1mb > per get is a lot of traffic... how can you hit that mark without saturation? > > Most people's keys are a lot smaller. In multiget tests with 40 byte keys > I can pull 20 million+ keys/sec out of the server. probably less than > 10gbps at that rate too. Tends to cap between 600k and 800k/s if you need > to do a full roundtrip per key fetch. limited by the NIC. Lots of tuning > required to get around that. > > In pure throughput over localhost I've gotten it past 78 gigabits.. using > 16k keys. > > it's pretty snappy. > > > > > On Aug 26, 2016 3:41 PM, "Ripduman Sohan" <[email protected]> > wrote: > > I believe it's standard memcached compared on kernel and > OpenOnload TCP stacks. I have had no involvement with this though so it's > just conjecture on my part. I > > guess [email protected] knows more, I can find out if it > helps. > > > > > > On 26 August 2016 at 23:37, dormando <[email protected]> wrote: > > Is that still using a modified codebase? > > > > On Fri, 26 Aug 2016, Ripduman Sohan wrote: > > > > > Some more numbers:https://www.solarflare.com/Media/Default/ > PDFs/Solutions/Solarflare-Accelerating-Memcached-Using- > Flareon-Ultra-server-IO-adapter.pdf > > > > > > On 26 August 2016 at 07:08, Henrik Schröder <[email protected]> > wrote: > > > Anecdotal datapoint: I have a machine with 2xE5520 (Xeon > server processor from 2009) which does ~300k requests/s, and handles > ~400Mbps of network > > traffic, but only > > > using ~5% of the CPU. > > > > > > It's been my experience that you will saturate your network way > before you'll saturate your CPU on pretty much any current hardware. > > > > > > > > > > > > On Thu, Aug 25, 2016 at 10:12 PM, Joseph Grasser < > [email protected]> wrote: > > > It is written in the docs that "On a fast machine with > very high speed networking, memcached can easily handle 200,000+ requests > per second." How fast > > does a > > > machine have to be in order to server that load easily? > What are the hardware requirements for such a server? > > > > > > https://github.com/memcached/memcached/wiki/Performance > > > > > > -- > > > > > > --- > > > 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. > > > > > > > > > -- > > > > > > --- > > > 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. > > > > > > -- > > > --rip > > > > > > -- > > > > > > --- > > > 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. > > > > > > > > > > -- > > > > --- > > 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. > > > > -- > > --rip > > > > -- > > > > --- > > You received this message because you are subscribed to a topic in the > Google Groups "memcached" group. > > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/memcached/la-0fH1UzyA/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > > > > --- > > 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. > > > > > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "memcached" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/memcached/la-0fH1UzyA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- 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.
