Domain separation performance considerations

  • リリースバージョン: Australia
  • 更新日 2026年03月12日
  • 所要時間：3分

    • 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:
    1. In the application navigator, enter sys_properties.list.
    2. Set the glide.ui.domain_reference_picker.enabled property to true.
    3. Refresh the browser.
    注:
    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.