[rabbitmq-discuss] Running StressPersister.java client against RabbitMQ and finding the stress_persister.log file is being "beaten to death"

[John Apps]

What parameters should one tweak in order to reduce the I/O to the log file
in the StressPersister test? And others with similar behaviour, of course.

The file grows to about 140MB using the default StressPersister parameters,
only to be renamed to stress_persister.log.previous and the whole cycle
starts again.
With smaller parameters than the default, i.e., smaller message size, lower
backlog etc., the pattern is the same, but the frequency with which the log
is renamed and recreated is faster.

What would be ideal would be to be able to specify an initial (large)
allocation for the file (so it does not extend it all the time) along with
an extension quantity, should it have to be extended. In addition, if one
could specify how much should be retained in memory prior to be flushed to
disk, that would also make things move along.

I have looked at a few mnesia and Erlang parameters but have not found the
right mix yet.

In case anyone asks, this is running Erlang (BEAM) emulator version 5.7 on
OpenVMS using Java 5.0 for the client.

Cheers, John
---
John Apps
(49) 171 869 1813
Sent from Traunstein, BY, Germany
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100119/e2631db9/attachment.htm