to find the bottleneck or time consuming within messenger moduleIt just like
"iperf", we need to start server-side program firstly:
-# ./ceph_perf_msgr_server 172.16.30.181:10001 0
+# ./ceph_perf_msgr_server 172.16.30.181:10001 1 0
The first argument is ip:port pair which is telling the destination address the
-client need to specified. The second argument tells the "think time" when
-dispatching messages. After Giant, CEPH_OSD_OP message which is the actual client
-read/write io request is fast dispatched without queueing to Dispatcher, in order
-to achieve better performance. So CEPH_OSD_OP message will be processed inline,
-"think time" is used by mock this "inline process" process.
+client need to specified. The second argument configures the server threads. The
+third argument tells the "think time"(us) when dispatching messages. After Giant,
+CEPH_OSD_OP message which is the actual client read/write io request is fast
+dispatched without queueing to Dispatcher, in order to achieve better performance.
+So CEPH_OSD_OP message will be processed inline, "think time" is used by mock
+this "inline process" process.
# ./ceph_perf_msgr_client 172.16.30.181:10001 1 32 10000 10 4096