Domain separation performance considerations
As you configure domain separation in your application and services, make sure that you consider the number and properties of domains you create. Too many property-heavy domains can impact the performance of your instance.
Limiting property-heavy domains
You can create as many domains as needed, but make sure that you don't create unnecessary domains on the instance. Weighing too many domains on the instance with a lot of properties can impact the performance of your instance.
The number of domains is not what impacts performance but rather what's in them. Too many properties can slow down the domain picker, which then slows down the overall user experience of your customers. If you are loading the domain picker and already have a large number of domains with a lot of properties, the domain picker has to load all the domains before it gives you control in the session. This process could lead to an outage where you can't access anything on the instance until the domain picker finishes. Before you create new domains, navigate to the domain hierarchy under Domain Admin > Domain Map and make sure that you actually need to create a new domain or whether an existing domain hierarchy can work.
Using Core UI domain picker
The domain reference picker is available in Core UI. With the reference picker, you do not load all the domains at once, but rather the domain is searched as you begin to enter the name of your domain into the domain picker.
Enable the domain reference picker in Core UI by following these steps:
- In the application navigator, enter
sys_properties.list. - Set the glide.ui.domain_reference_picker.enabled property to true.
- Refresh the browser.
Note: Do not upload a large number of domains (over 30) via integration or import sets without doing some testing first or you might bring down your instance.
Parent Topic:Domain separation recommended practices for service providers
Related topics
Segregating and securing data with domain separation
Alternatives to domain separation
Evaluating the need for domain separation
How a database query works with domain separation
Domain separation levels of support
Service provider reference architecture
Domain-separate a custom table
Customizing domain properties and themes
Managing domain separation for specific uses
Configuring domain separation with the domain picker
Checking domain logs for errors and warnings
Importance of the Default domain
Contains queries and domain access
Slow queries and SQL debugging
Avoiding domain path in scripts
Domain separation and the Customer Service Management (CSM) plugin