Correction ""./memcached -l notls:*:11211,*:22122 -Z -o ssl...". Memcached will start with TLS on port 22122 and no TLS at port 11211.
On Friday, 18 December 2020 at 10:53:52 UTC-8 Tharanga Gamaethige wrote: > A good starting point is mccrusher : > https://github.com/memcached/mc-crusher. "make" vs "make tls" will give > you the corresponding client (mc-crusher vs mc-crusher-tls). Running > mc-crusher and related tools to benchmark latency and throughput is > explained in the README file. > Note that you can run memcached with and without TLS at the same time. e.g > "./memcached -l notls:*:11211,*:22122". So you don't have to stop/start > memcached for different tests. Also note that you need to run like this > when capturing TLS numbers as tools provided with mc-crusher such as > latency-sampler need a non-TLS socket to connect. > > Keep in in mind that this is very basic test suit. > > On Thursday, 17 December 2020 at 08:06:02 UTC-8 [email protected] wrote: > >> t would be good if I get some clear steps to run the performance analysis >> of Memcached with TLS and also without TLS. >> >> On Thursday, December 17, 2020 at 8:44:54 PM UTC+5:30 avinash pandian >> wrote: >> >>> Dear Team, >>> >>> I would like to know how to check the performance of Memcached without >>> TLS and also after enabling TLS. >>> Requesting you support in achieving the same so that it would be really >>> help for me to proceed further. >>> >>> Awaiting for your reply. Thanks in advance >>> >>> Regards, >>> Avinash Chellapandian >>> >>> -- --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/memcached/a629b75d-6633-4031-87e2-95bb8fa5e167n%40googlegroups.com.
