> What did you try tuning? We have only tuned the page sizes and number of pages (page-size-bytes, page-max-cache-size), we have also tried adjusting the JVM -Xmx size and global-max-size. We saw no difference adjusting the paging values and the amount of memory we have on our test bench is about 100 times short of what we would require.
> Did you gather any metrics from the broker during the slow-down (e.g. GC logging, thread dumps, etc.)? If so, what did you find? Our benchmark is set to record the producer rate and as it goes into paging mode (indicated in Artemis log) we see a big impact on throughput. If you could help us understand which metrics might be of interest and how can they help us, we'd really appreciate it. > What measures are you taking to ensure the consumers will be able to catch > up and clear that backlog? When re-introducing a consumer to pick up the messages we have seen it consume messages at a rate much higher than messages are being produced, which suggests batching being performed. So we are confident a consumer would be able to catch up with the backlog. However once in paging "mode" the producer seems stuck and never recovers the original throughput. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
