You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This way PerfTest will use 12 threads for I/O over all the connections.
410
-
With the default blocking I/O mode, each producer (or consumer)
411
-
uses a thread for the I/O loop, that is 2000 threads to simulate 1000 producers and
412
-
1000 consumers. Using NIO in PerfTest can dramatically reduce the resources used
413
-
to simulate workloads with a large number of connections with appropriate tuning.
414
-
415
-
Note that in NIO mode the number of threads used can increase temporarily when connections close
416
-
unexpectedly and connection recovery kicks in. This is due to the NIO mode dispatching
417
-
connection closing to non-I/O threads to avoid deadlocks. Connection recovery can be disabled
418
-
with the `--disable-connection-recovery` flag.
419
-
409
+
This way PerfTest will use 10 threads for I/O over all the connections.
410
+
With the default blocking I/O mode, each producer (or consumer) uses a thread for the I/O loop, that is 2000 threads to simulate 1000 producers and 1000 consumers.
411
+
Using Netty in PerfTest can dramatically reduce the resources used to simulate workloads with a large number of connections with appropriate tuning.
420
412
421
413
== Running Producers and Consumers on Different Machines
0 commit comments