diff options
| author | Matthew Sackman <matthew@lshift.net> | 2009-06-19 17:52:00 +0100 |
|---|---|---|
| committer | Matthew Sackman <matthew@lshift.net> | 2009-06-19 17:52:00 +0100 |
| commit | ae6989591b7a6e430a4f4c6ec4e51ebb15377b38 (patch) | |
| tree | e29ed0ad9a77be61703bc50a21bc29291907946d /scripts/rabbitmq-multi | |
| parent | 6096fe52182b61165a5f36fe87c44730e645e2fa (diff) | |
| download | rabbitmq-server-git-ae6989591b7a6e430a4f4c6ec4e51ebb15377b38.tar.gz | |
Just added a means to get the ets:info out for the cache. Testing shows that it does seem to get emptied successfully.
So, using this revision, if you run:
rabbitmq-java-client/build/dist$ sh runjava.sh com/rabbitmq/examples/MulticastMain -y 10 -r 50 -s 1048576 -m 100 -z 120
then over the two mins, I see beam take between about 30% and 45% of my memory, once it's up and running.
Using the revision right after the API change, i.e. 9f0ee0399838, the same test tries to take between about 45% and 60% of my memory.
Don't forget to run:
rabbitmq-server$ ./scripts/rabbitmqctl reduce_memory_footprint
rabbitmq-server$ ./scripts/rabbitmqctl reduce_memory_footprint
before running the above test.
Diffstat (limited to 'scripts/rabbitmq-multi')
0 files changed, 0 insertions, 0 deletions