NetX aggressively caches data within the application, which in turns makes the application much more responsive. These caches can be tuned either by navigating to the Caches section within the UI, or by making modifications to the following properties:
|Object||Property||Default||Notes and recommendations|
|Asset||image.cache_size_asset||10000||This is the main cache that you may want to adjust. Please appreciate that increasing this will potentially increase the need for a larger Java memory heap. However, for very large installations, setting this to a value of 100,000 is common. But, it is not usually advised to set this much higher than that; at a certain point the size of the cache will work against itself, and the application responsiveness will suffer. Also see the "asset.keepCacheFull" property in the section below.|
|Attributes||image.cache_size_attribute||1000||This cache is largely unused, other than managing the cache of Attribute Templates. Unless you have more than 1000 attributes defined (which would be extraordinary), please leave this cache at the default.|
|Category||image.cache_size_category||*||It's better if you allow the application to manage this property value. On startup, it will auto-adjust this cache value to 10% more than the total number of categories that exist in the system. This value should never be set below the total number of categories in the system because the application relies on maintaining the entire category structure in-memory, and at all times.|
|File Type||image.cache_size_file_type||1000||This cache should only be changed if directed to do so by NetX Support.|
|Location||image.cache_size_location||1000||This cache should only be changed if directed to do so by NetX Support.|
|Group||image.cache_size_group||1000||This cache should only be changed if directed to do so by NetX Support.|
|User||1000||If you have a tremendously large number of users that frequently login, you may want to increase the size of this cache to better support your deluge of users. Typically, the default is plenty.|
|User Login||image.cache_size_user_login||1000||If you have a tremendously large number of users that frequently login, you may want to increase the size of this cache to better support your deluge of users. Typically, the default is plenty.|
Automatically fill the asset cache
To enable auto cache filling, set this property to "true":
Please note: this will be auto-enabled in 8.12.
Second, add this property to automatically fill your asset cache:
Adding this, and setting it to "true", NetX will periodically fill the asset cache to approximately 50 percent of capacity.
Please note: this will default to 10% in 8.12.
To increase the percent to fill of your asset cache, set this property to a number between 1 and 85:
For example, if you have your Asset cache set at 100,000, and you set this property to "50", then NetX will work to keep the Asset cache filled to 50,000 every 15 minutes.
This may require NetX to be configured with more memory, but it may also speed up search results.
The auto-cache filling for Assets system attempts to add assets that are most used first. To accomplish this, the order of preference is as follows:
- Load assets that have been part of folder lists in the last 30 days
- Load assets that have been previewed in the last 30 days
- Fill remaining cache threshold based on modification date of the asset.