$./cpgbench54115 messages received 1 bytes per write 10.004 Seconds runtime 5409.525 TP/s 0.005 MB/s. 21050 messages received 1001 bytes per write 10.000 Seconds runtime 2105.062 TP/s 2.107 MB/s. 22864 messages received 2001 bytes per write 10.000 Seconds runtime 2286.301 TP/s 4.575 MB/s. 42131 messages received 3001 bytes per write 10.000 Seconds runtime 4213.216 TP/s 12.644 MB/s. 55599 messages received 4001 bytes per write 10.000 Seconds runtime 5560.081 TP/s 22.246 MB/s. 51113 messages received 5001 bytes per write 10.000 Seconds runtime 5111.492 TP/s 25.563 MB/s. 10245 messages received 6001 bytes per write 10.000 Seconds runtime 1024.538 TP/s 6.148 MB/s. 0 messages received 7001 bytes per write 10.000 Seconds runtime 0.000 TP/s 0.000 MB/s.
At the time the message rate go down on the corosync log: Aug 22 9:59:57.590518 [IPC ] Enabling flow control [401/800] - [0]. Aug 22 9:59:57.753496 [IPC ] Disabling flow control [403/800] - [0].to my understanding flow control will slow down when overflowed but restart the flow when ready to process more data?
Fabien
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
