Michal Kuratczyk
Michal Kuratczyk
With the most recent changes I get these results (same machines as above): linux: 103000 / 73000 / 920000 macos: 80000 / 40000 / 840000 So indeed some tests are...
Only a quick and dirty test for now but: setting `+hmbs` (default virtual binary heap) doesn't change anything but setting `+hms` (default heap size) restores the performance of OTP26 in...
Yes, we still haven't merged any fixes for this so RabbitMQ on OTP27 works, but is significantly slower for some message sizes (from 65 bytes up to 1-2kb - above...
Regarding vhosts, I think we can indeed use existing vhost tags and emit a `rabbitmq_vhost_info` metric with these tags as labels. For queues, in RabbitMQ 4.1, `rabbitmq_queue_info` metric gets introduced...
I think another path is this: 1. a developer with no RabbitMQ experience joins a team/company where RabbitMQ is used 2. there's already an app that uses RabbitMQ, therefore the...
Message size metrics were introduced in RabbitMQ 4.1 https://github.com/rabbitmq/rabbitmq-server/pull/12342
I'm not sure if that the problem or a part of the problem, but `v3.13.x` is now compatible with OTP27. It's still not supported to run RabbitMQ on OTP27 (or...
We don't have a separate separate policy for the client but starting with the next version, 3.13.x should compile using OTP27 (since the PR I mentioned above was merged after...
Sounds similar to https://github.com/rabbitmq/rabbitmq-server/pull/10931. Perhaps this PR solved this problem for some, but not all metrics?
closing in favour of https://github.com/rabbitmq/cluster-operator/pull/1865