Enable Site Settings Cache

(This feature can be tried with the Pleasanter Extensions Trial.)

Overview¶

Each time a table is referenced or updated, Pleasanter reads the site settings, which hold the settings of the table, from the database. The more complex the link structure, with many tables referencing each other, the more this reading may affect performance.

This feature caches the site settings once they are read in the memory of the web server and reuses them in later processing. They are not persisted to the database, a KVS, or anywhere else. This choice gives priority to processing speed, and the cache is cleared when the server restarts. This reduces the number of accesses to the database and improves performance.

The cache can be enabled for each table. You can turn it on or off according to the structure and the operating conditions of the table.

Cases Where the Effect Is Large and Cases Where It Is Small¶

The following processes read the site settings repeatedly, so the cache has a large effect.

1. Processes that repeat references and updates through the API (such as running your own batch programs)
2. Repeated scrolling on the list screen
3. Work by a small number of users that repeats displaying the list, referencing and updating on the edit screen, and creating new records

The following processes read the site settings only once, so the cache has a small effect.

1. Import and export (both on the screen and through the API)
2. Bulk update (screen), bulk create and update (API), and bulk delete (both on the screen and through the API)

In these processes, the number of records does not affect how many times the site settings are read. Whether one record or 10,000 records are processed, the site settings are read only once. The cache is held for each user ID. For this reason, the cache also has little effect when many users each perform an operation only once (such as many users submitting a survey). Each user only ever accesses their own cache for the first time.

Limitations¶

1. The effect of this feature differs depending on the processing pattern. Verify it thoroughly before using it.

Prerequisites¶

1. This feature is available only to subscribers of the following plans of the Annual Support Service.

Operation Procedure¶

You can enable the site settings cache on the screen or through the API. For details, see the following pages.

Supported Versions¶