Performance in Business Central Online
These sections describe how settings in Business Central online impact the performance experience of users.
Performance on sandbox environments
The Business Central service offers the ability to test code in a sandbox environment before to deploying to a production environment.
Users often can't get the same performance and reliability in Business Central online as they get in their production environments. This discrepancy is caused by a couple factors.
Firstly, it's the nature of the operations that our users do in the sandbox environments. Some typical examples of this are:
- Frequent publishing and installation of per-tenant extensions (PTEs), which aren't yet of production quality
- Creating multiple companies for different users to try their scenarios
- Initializing test environments with data via RapidStart
Secondly, it is because the sandbox services configuration. Sandbox configurations tend to be more dense and have different thresholds than production. Read more about sandboxes in Managing Environments.
Large-scale cloud services use shared resources to achieve the best possible use of resources – like IO, CPU, and memory. To ensure that tenants run smoothly, limits are applied to various operations. These limits control things like: how long an operation can run before being canceled, or how many operations can run at the same time. Some of the operations include:
- Web service requests
- Report and query generation
- Client connections
- Background task execution
Without limits, one tenant could use many more resources than other tenants. Other tenants running on the same resources might experience slower performance. Although you can't change these limits, it's useful to be aware of them. For more information about the limits, see Operational Limits for Business Central Online.