First, you need to make sure that you have high enough open file limit for the user running imaptest by doing something like: ulimit -n 65535 (this might also require editing nofile in /etc/security/limits.conf accordingly).
For very intense load testing it's also possible to run out of TCP sockets so setting sysctl -w net.ipv4.tcp_tw_reuse=1 helps.
<CR><LF> terminated mbox format file to use for source emails
Profile configuration file
Number of concurrent clients
(OPTIONAL) For IMAP testing, this can be specified to only send a single IMAP command at a time and wait for a response before sending the next one. This should be used to get accurate IMAP latencies.
(OPTIONAL) Number of seconds to run the test. If not specified, the process must be ended manually either with Ctrl+c (if there are stuck connections and you want to force it to end, use ctrl+c twice) or killing the process directly.
The warning can be ignored because we are intentionally throttling the number of LMTP connections in this configuration.
There is a line of output every second that is showing the number of commands sent per command. See states for an explanation of each column.
Every 10 seconds a line is output showing average duration per connection. This is the most important one to watch; if the ms/cmd starts increasing then this indicates an issue with the platform. If everything is operating normally it should remain approximately the same for all commands.
At exit, the total number of operations performed during the test is output.