https://www.rabbitmq.com/assets/js/a0792d03.1ddce61d.js

1"use strict";(self.webpackChunkrabbitmq_website=self.webpackChunkrabbitmq_website||[]).push([["17634"],{41078(e,t,n){n.r(t),n.d(t,{assets:()=>l,contentTitle:()=>a,default:()=>m,frontMatter:()=>s,metadata:()=>i,toc:()=>b});var i=n(21522),o=n(74848),r=n(28453);let s={title:"Finding bottlenecks with RabbitMQ 3.3",tags:["Performance","New Features"],authors:["simon"]},a,l={authorsImageUrls:[void 0]},b=[];function u(e){let t={p:"p",...(0,r.R)(),...e.components};return(0,o.jsx)(t.p,{children:"One of the goals for RabbitMQ 3.3 was that you should be able to find bottlenecks in running systems more easily. Older versions of RabbitMQ let you see that you were rate-limited but didn't easily let you see why. In this blog post we'll talk through some of the new performance indicators in version 3.3."})}function m(e={}){let{wrapper:t}={...(0,r.R)(),...e.components};return t?(0,o.jsx)(t,{...e,children:(0,o.jsx)(u,{...e})}):u(e)}},28453(e,t,n){n.d(t,{R:()=>s,x:()=>a});var i=n(96540);let o={},r=i.createContext(o);function s(e){let t=i.useContext(r);return i.useMemo(function(){return"function"==typeof e?e(t):{...t,...e}},[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:s(e.components),i.createElement(r.Provider,{value:t},e.children)}},21522(e){e.exports=JSON.parse('{"permalink":"/blog/2014/04/14/finding-bottlenecks-with-rabbitmq-3-3","editUrl":"https://github.com/rabbitmq/rabbitmq-website/tree/main/blog/2014-04-14-finding-bottlenecks-with-rabbitmq-3-3/index.md","source":"@site/blog/2014-04-14-finding-bottlenecks-with-rabbitmq-3-3/index.md","title":"Finding bottlenecks with RabbitMQ 3.3","description":"One of the goals for RabbitMQ 3.3 was that you should be able to find bottlenecks in running systems more easily. Older versions of RabbitMQ let you see that you were rate-limited but didn\'t easily let you see why. In this blog post we\'ll talk through some of the new performance indicators in version 3.3.","date":"2014-04-14T00:00:00.000Z","tags":[{"inline":true,"label":"Performance","permalink":"/blog/tags/performance"},{"inline":true,"label":"New Features","permalink":"/blog/tags/new-features"}],"readingTime":3.89,"hasTruncateMarker":true,"authors":[{"name":"Simon MacMullen","key":"simon","page":null}],"frontMatter":{"title":"Finding bottlenecks with RabbitMQ 3.3","tags":["Performance","New Features"],"authors":["simon"]},"unlisted":false,"prevItem":{"title":"Understanding memory use with RabbitMQ 3.4","permalink":"/blog/2014/10/30/understanding-memory-use-with-rabbitmq-3-4"},"nextItem":{"title":"Consumer Bias in RabbitMQ 3.3","permalink":"/blog/2014/04/10/consumer-bias-in-rabbitmq-3-3"}}')}}]);