<html><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div>Matthias,</div><div><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">> i increased the timeout of login from 10 sec to 5 minutes, then the<br></div><div style="font-size: 12pt; font-family: times new roman,new york,times,serif;"><div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">> consumers could consume the 200 GB of messages without any problems. the<br>> 2.1.1 broker's memory kept below 6.2 GB. (the memory usage for release<br>> 2.0.0 was 10 GB for this test case).<br><br>There is another problem: The broker's memory usage grew from 6.2GB to 10 GB 1 hour after the consumers were started.<br>This caused swapping and the consume rate dropped from 30 MB/sec to less than 10 MB/sec. I think
the broker only throttles the publisher when the mem high water mark is reached, but the consumers can still increase the broker's mem usage?<br>if this cannot be avoided, we have to increase the RAM to 16GB.<br><br>thanks.<br><br>-alex<br><br><br></div></div></div><br>
</body></html>