# Dimensioning of a HiveMQ CE Broker **URL:** \ **Category:** HiveMQ Community Edition\ **Created:** [June 7, 2022, 3:33pm UTC](https://community.hivemq.com/t/dimensioning-of-a-hivemq-ce-broker/1248 "2022-06-07T15:33:59Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![sanjmeh](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/sanjmeh/32/305_2.png) [@sanjmeh](https://community.hivemq.com/u/sanjmeh)\ **Post date:** [June 7, 2022, 3:34pm UTC](https://community.hivemq.com/t/dimensioning-of-a-hivemq-ce-broker/1248/1 "2022-06-07T15:34:00Z")
I am dimensioning a HiveMQ CE broker on Ubuntu 20 with following connections and peak traffic: - Total 500 PUB client ids, - Total 500 SUB client ids, - Total 2500 topics - 5MB per day per client message size - One message every 60 seconds per topic - Average size per message : 800 Bytes - 3 Million messages per day - max queue size: 300,000 messages (not sure how close this will be to reality) I want to know how to arrive at ballpark numbers for RAM, vCPUs, Bandwidth and disk storage. I use Digital Ocean as my cloud infra provider but the answer would be valid for AWS as well. Appreciate if you can also mention what heuristic/thumb rule you used to arrive at the capacity. Thanks ---
**Author:** ![michael\_w](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/michael_w/32/200_2.png) [@michael\_w](https://community.hivemq.com/u/michael_w)\ **Post date:** [June 7, 2022, 3:45pm UTC](https://community.hivemq.com/t/dimensioning-of-a-hivemq-ce-broker/1248/2 "2022-06-07T15:45:36Z")
Hi @sanjmeh, giving a rule of thumb is always hard to give because the needed capacity always depends so much factors. But in your case I think you are definitely good to go with the minimum requirement aka 4 CPU’s 8gb RAM (in AWS terms this would be a c5.xlarge ec2 instance). Greetings, Michael from the HiveMQ team