In WSO2 products based on Carbon 4.4.0 or later versions, you have the option of setting the required tenant loading policy by enabling either Lazy Loading or Eager Loading of tenants.
- Lazy Loading: Lazy loading is a design pattern used specifically in cloud deployments to prolong the initialisation of an object until it is requested by a tenant or an internal process. Lazy loading of tenants is a feature that is built into all WSO2 products, which ensures that in an environment with multiple tenants, all tenants are not loaded at the time the server starts. Instead, they are loaded only when a request is made to a particular tenant. If a tenant is not utilised for a certain period of time, it will be unloaded from memory.
- Eager Loading: Eager loading is is a design pattern commonly used in computer programming. As opposed to lazy loading, eager loading initialises an object upon creation. If Eager loading is enabled in WSO2 products, existing tenants will be loaded without any delays when the Carbon server starts. You can also enable this feature for specific tenants, so that only the required tenants will be loaded when the server starts.
...
Configuring the Lazy Loading idle time
If you are using the default tenant loading policy (Lazy Loading), you have the option of setting the required tenant idle time. For example, if you set the idle time to 30 minutes, tenants that are idle for more than 30 minutes will be unloaded automatically in your system.
...