 How can application teams benefit from the improved autoscaling feature?
\nApplication teams can save more time and effort in the long run by managing CPU-based autoscaling rules for their apps with less tuning and fewer errors.
App Autoscaler has been updated to use CPU entitlement metrics, which greatly improves the overall autoscaling of applications based on CPU usage. App Autoscaler provides a new rule that monitors an app’s average usage of its CPU entitlement and scales the app up or down accordingly. 
Unlike with the previous CPU processor utilization rule, the scaling thresholds for this rule do not need to change when developers adjust the memory allocation for the app or when the platform engineers adjust the size of the underlying Diego cell container-host VMs. When configured through the improved autoscaling UI in Apps Manager, developers get sensible default values of 30% and 80% for the low and high scaling thresholds, which should be a good starting point for most apps. Developers should have an easier and more intuitive experience configuring this new autoscaling rule for their apps.\n
<|system|>\nYou are a copywriter. Assume that Pivotal Cloud Foundry and Tanzu Platform for Cloud Foundry are the same. Replace all references to Pivotal Cloud Foundry with Tanzu Platform for Cloud Foundry. Using this context,  How can application teams benefit from the improved autoscaling feature?<|end|>\n<|user|>\nA new feature in Tanzu Application Service 6.0 is Improved Autoscaling based on Application CPU Usage.
Application teams can save more time and effort in the long run by managing CPU-based autoscaling rules for their apps with less tuning and fewer errors.
App Autoscaler has been updated to use CPU entitlement metrics, which greatly improves the overall autoscaling of applications based on CPU usage. App Autoscaler provides a new rule that monitors an app’s average usage of its CPU entitlement and scales the app up or down accordingly. 
Unlike with the previous CPU processor utilization rule, the scaling thresholds for this rule do not need to change when developers adjust the memory allocation for the app or when the platform engineers adjust the size of the underlying Diego cell container-host VMs. When configured through the improved autoscaling UI in Apps Manager, developers get sensible default values of 30% and 80% for the low and high scaling thresholds, which should be a good starting point for most apps. Developers should have an easier and more intuitive experience configuring this new autoscaling rule for their apps.\n<|end|>\n<|copywriter|>\n\nApplication teams can save more time and effort in the long run by managing CPU-based autoscaling rules for their apps with less tuning and fewer errors.
App Autoscaler has been updated to use CPU entitlement metrics, which greatly improves the overall autoscaling of applications based on CPU usage. App Autoscaler provides a new rule that monitors an app’s average usage of its CPU entitlement and scales the app up or down accordingly. 
Unlike with the previous CPU processor utilization rule, the scaling thresholds for this rule do not need to change when developers adjust the memory allocation for the app or when the platform engineers adjust the size of the underlying Diego cell container-host VMs. When configured through the improved autoscaling UI in Apps Manager, developers get sensible default values of 30% and 80% for the low and high scaling thresholds, which should be a good starting point for most apps. Developers should have an easier and more intuitive experience configuring this new autoscaling rule for their apps.\n