Hi sagar Thanks for reaching out. The performance of Azure Service Bus Premium tier depends on several factors, including the number of messages being processed, the size of the messages, and the configuration of your Service Bus namespace.
If your application generates and consumes around 3000 messages per second in a test environment and 10000 messages per second in a production environment, you may need to scale up your Service Bus namespace to handle the increased workload. You can use the Azure portal or Azure CLI to scale up your Service Bus namespace by increasing the number of messaging units (MUs1).
If you configure your Service Bus namespace with 1 MU and do not enable auto scaling, the high usage of Memory/CPU will not cause message lost. However, incoming messages will be throttled you can reduce the possibility of getting throttled by scaling up the number of messaging units allocated to your namespace in the event (or anticipation) of a spike in the workload. please refer : https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-throttling#how-does-throttling-work-in-service-bus-premium
https://learn.microsoft.com/en-us/azure/architecture/patterns/throttling#solution
The CPU utilization of your Service Bus namespace is based on the number of messages being processed (number of messages that are being sent, received, or processed by a Service Bus entity), as well as other factors such as the size of the messages and the configuration of your namespace.
Hope this helps! Let me know in case of further queries, I would be happy to assist you.
Please "upvote/accept" if the answer is helpful so that it can help others in the community.