Memcached instance and thread configuration parameters
I have this Memcached cluster where 3 instances of Memcached run in a single server. These servers have 24 cores, each instance is configured to have 8 threads each. Each individual instance serves have about 5000G gets/sets a day and about 3k current connections. What would be better? consolidate these 3 instances to a single instance per server with 24 threads? I've read in a few articles that Memcached's performance starts suffering with more than 4-6 threads per instance, is this generally true? How about keeping the 3 instances per server and decreasing the number of threads to say 4 or 6? or creating 4 instances in the same servers instead of 3 and decreasing the number of threads per instance to 6 so there is one thread per core. Is there a guide you could recommend to configure the right number of threads and strategies to get the most out of a Memcached server/instance? Thanks, Claudio -- --- 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Memcached instance and thread configuration parameters
On Mon, 4 Aug 2014, Claudio Santana wrote: > I have this Memcached cluster where 3 instances of Memcached run in a single > server. These servers have 24 cores, each instance > is configured to have 8 threads each. Each individual instance serves have > about 5000G gets/sets a day and about 3k current > connections. I don't know what "5000G gets/sets a day" translates to in per-second (nor what the G-unit even is?), can you define this? > What would be better? consolidate these 3 instances to a single instance per > server with 24 threads? I've read in a few articles > that Memcached's performance starts suffering with more than 4-6 threads per > instance, is this generally true? > > How about keeping the 3 instances per server and decreasing the number of > threads to say 4 or 6? or creating 4 instances in the > same servers instead of 3 and decreasing the number of threads per instance > to 6 so there is one thread per core. > > Is there a guide you could recommend to configure the right number of threads > and strategies to get the most out of a Memcached > server/instance? > > Thanks, > Claudio > > -- > > --- > 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 memcached+unsubscr...@googlegroups.com. > 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Memcached instance and thread configuration parameters
I don't have exact metrics per second but per minute 1.1 million sets and 1.8 million gets which translates to On Mon, Aug 4, 2014 at 6:22 PM, dormando wrote: > On Mon, 4 Aug 2014, Claudio Santana wrote: > > > I have this Memcached cluster where 3 instances of Memcached run in a > single server. These servers have 24 cores, each instance > > is configured to have 8 threads each. Each individual instance serves > have about 5000G gets/sets a day and about 3k current > > connections. > > I don't know what "5000G gets/sets a day" translates to in per-second (nor > what the G-unit even is?), can you define this? > > > What would be better? consolidate these 3 instances to a single instance > per server with 24 threads? I've read in a few articles > > that Memcached's performance starts suffering with more than 4-6 threads > per instance, is this generally true? > > > > How about keeping the 3 instances per server and decreasing the number > of threads to say 4 or 6? or creating 4 instances in the > > same servers instead of 3 and decreasing the number of threads per > instance to 6 so there is one thread per core. > > > > Is there a guide you could recommend to configure the right number of > threads and strategies to get the most out of a Memcached > > server/instance? > > > > Thanks, > > Claudio > > > > -- > > > > --- > > 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 memcached+unsubscr...@googlegroups.com. > > 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 memcached+unsubscr...@googlegroups.com. > 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Memcached instance and thread configuration parameters
Dormando, thanks for the quick response. Sorry for the confusion, I don't have exact metrics per second but per minute 1.12 million sets and 1.8 million gets which translates to 18,666 sets per minute and 30,000 gets per second. These stats are per Memcached instance which I currently run 3 on each server. Claudio. On Mon, Aug 4, 2014 at 6:22 PM, dormando wrote: > On Mon, 4 Aug 2014, Claudio Santana wrote: > > > I have this Memcached cluster where 3 instances of Memcached run in a > single server. These servers have 24 cores, each instance > > is configured to have 8 threads each. Each individual instance serves > have about 5000G gets/sets a day and about 3k current > > connections. > > I don't know what "5000G gets/sets a day" translates to in per-second (nor > what the G-unit even is?), can you define this? > > > What would be better? consolidate these 3 instances to a single instance > per server with 24 threads? I've read in a few articles > > that Memcached's performance starts suffering with more than 4-6 threads > per instance, is this generally true? > > > > How about keeping the 3 instances per server and decreasing the number > of threads to say 4 or 6? or creating 4 instances in the > > same servers instead of 3 and decreasing the number of threads per > instance to 6 so there is one thread per core. > > > > Is there a guide you could recommend to configure the right number of > threads and strategies to get the most out of a Memcached > > server/instance? > > > > Thanks, > > Claudio > > > > -- > > > > --- > > 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 memcached+unsubscr...@googlegroups.com. > > 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 memcached+unsubscr...@googlegroups.com. > 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Memcached instance and thread configuration parameters
You could run one instance with one thread and serve all of that just fine. have you actually looked at graphs of the CPU usage of the host? memcached should be practically idle with load that low. One with -t 6 or -t 8 would do it just fine. On Mon, 4 Aug 2014, Claudio Santana wrote: > Dormando, thanks for the quick response. Sorry for the confusion, I don't > have exact metrics per second but per minute 1.12 > million sets and 1.8 million gets which translates to 18,666 sets per minute > and 30,000 gets per second. > > These stats are per Memcached instance which I currently run 3 on each server. > > Claudio. > > > On Mon, Aug 4, 2014 at 6:22 PM, dormando wrote: > On Mon, 4 Aug 2014, Claudio Santana wrote: > > > I have this Memcached cluster where 3 instances of Memcached run in a > single server. These servers have 24 cores, > each instance > > is configured to have 8 threads each. Each individual instance serves > have about 5000G gets/sets a day and about > 3k current > > connections. > > I don't know what "5000G gets/sets a day" translates to in per-second (nor > what the G-unit even is?), can you define this? > > > What would be better? consolidate these 3 instances to a single instance > > per server with 24 threads? I've read in a few > articles > > that Memcached's performance starts suffering with more than 4-6 threads > > per instance, is this generally true? > > > > How about keeping the 3 instances per server and decreasing the number of > > threads to say 4 or 6? or creating 4 instances > in the > > same servers instead of 3 and decreasing the number of threads per instance > > to 6 so there is one thread per core. > > > > Is there a guide you could recommend to configure the right number of > > threads and strategies to get the most out of a > Memcached > > server/instance? > > > > Thanks, > > Claudio > > > > -- > > > > --- > > 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 > memcached+unsubscr...@googlegroups.com. > > 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 memcached+unsubscr...@googlegroups.com. > 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 memcached+unsubscr...@googlegroups.com. > 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
memcached local vs AWS ElasticCache (memcached)
Can someone in this group point me to the comparison for failover support provided in the below 2 cases : 1. Running a memcached server on a local machine with spymemcached client . 2. Running a AWS memcached server and accessing it on EC2 instance with spymemcached client . Also please let me know if any other client is preferred over spymemcached for handling failovers. Regards, Prasad -- --- 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
