Linux s390 Architecture development
 help / color / mirror / Atom feed
From: liuyacan@corp.netease.com
To: kgraul@linux.ibm.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Cc: linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, ubraun@linux.ibm.com,
	tonylu@linux.alibaba.com
Subject: SMC-R problem under multithread
Date: Mon, 30 May 2022 11:16:04 +0800	[thread overview]
Message-ID: <20220530031604.144875-1-liuyacan@corp.netease.com> (raw)

Hi experts,

  I recently used memcached to test the performance of SMC-R relative to TCP, but the results 
  are confusing me. When using multithread on the server side, the performance of SMC-R is not as good as TCP.
    
  Specifically, I tested 4 scenarios with server thread: 1\2\4\8. The client uses 8threads fixedly. 
  
  server: (smc_run) memcached -t 1 -m 16384 -p [SERVER-PORT] -U 0 -F -c 10240 -o modern
  client: (smc-run) memtier_benchmark -s [SERVER-IP] -p [SERVER-PORT] -P memcache_text --random-data --data-size=100 --data-size-pattern=S --key-minimum=30 --key-maximum=100  -n 5000000 -t 8
  
  The result is as follows:
  
  SMC-R:
  
  server-thread    ops/sec  client-cpu server-cpu
      1             242k        220%         97%
      2             362k        241%        128%
      4             378k        242%        160%
      8             395k        242%        210%
      
  TCP:
  server-thread    ops/sec  client-cpu server-cpu
      1             185k       224%         100%
      2             435k       479%         200%
      4             780k       731%         400%
      8             938k       800%         659%                   
   
  It can be seen that as the number of threads increases, the performance increase of SMC-R is much slower than that of TCP.

  Am I doing something wrong? Or is it only when CPU resources are tight that SMC-R has a significant advantage ?  
  
  Any suggestions are welcome.


Thanks & Regards,
Yacan.


             reply	other threads:[~2022-05-30  3:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30  3:16 liuyacan [this message]
2022-05-30  5:10 ` SMC-R problem under multithread Tony Lu
2022-05-30  6:40   ` liuyacan
2022-05-30  8:24     ` Tony Lu
2022-05-31  7:02       ` liuyacan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220530031604.144875-1-liuyacan@corp.netease.com \
    --to=liuyacan@corp.netease.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kgraul@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=ubraun@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox