Added explanation and guidance around performance scaling

Author: EldertGrootenboer

articles/service-bus-messaging/service-bus-performance-improvements.md

@@ -47,7 +47,7 @@ The benchmarking sample doesn't use any advanced features, so the throughput you
 
 #### Compute considerations
 
-Using certain Service Bus features require compute utilization that can decrease the expected throughput. Some of these features are -
+Service Bus operates several background processes that can affect compute utilization. These include, but are not limited to, timers, schedules, and metrics emission. Additionally, using certain Service Bus features require compute utilization that can decrease the expected throughput. Some of these features are -
 
 1. Sessions.
 2. Fanning out to multiple subscriptions on a single topic.
@@ -58,9 +58,7 @@ Using certain Service Bus features require compute utilization that can decrease
 7. Deduplication & look back time window.
 8. Forward to (forwarding from one entity to another).
 
-If your application uses any of the above features and you aren't receiving the expected throughput, you can review the **CPU usage** metrics and consider scaling up your Service Bus Premium namespace.
-
-You can also utilize Azure Monitor to [automatically scale the Service Bus namespace](automate-update-messaging-units.md).
+If your application uses any of the above features and you aren't receiving the expected throughput, you can review the **CPU usage** metrics and consider scaling up your Service Bus Premium namespace. You can also utilize Azure Monitor to [automatically scale the Service Bus namespace](automate-update-messaging-units.md). It is advisable to increase the number of Message Units (MUs) when CPU usage exceeds 70% to ensure optimal performance.
 
 ### Sharding across namespaces