Cache

The Cache options let you manage persistence cache activation, resources and monitoring.

This section explains how to customize persistence Cache settings.The persistence Cache keeps the streams accessed or saved during a session on a local directory in order to speed up successive data loading.

It also guarantees the consistency of the runtime session and is part of the LocalSave functionality.

  • The first time you need an applicatvie srteam it is downloaded from the repository both into the cache and the opened session.
  • The next times you need the same string, it is reopened in session directly from the cache.
Important: Storing data on disk could be an issue regarding the security rules of a customer company, there are two ways to protect data:

  • Native protection of the OS.
  • Encrypt documents (for example, Windows BitLocker): the customer can implement encryption / decryption protocols.

This cache is permanent: data are kept in physical disk space during two or more sessions, which reduces the transfers from the Vault (Data repository) and the loading time. It is possible to add a size limit management (see the details of these options below). This Cache is optional but if any, it must always be defined locally on each user's workstation and must not be shared with other users.

The size estimation for the session Caches is the maximum size of the streams that a given user can load during a session. This value is variable and strongly linked to the user's activity.

Note: Cache settings parameters can be locked by an administrator.

The edition of these values in the middle of a session is strongly forbidden. To edit them:

  • Open a session: do not open any component in session.
  • Edit the Cache parameters.
  • Restart the application to take current change into account.
  • Close the session without saving anything.
  • Open a working session: new parameters are taken into account.

Persistence Cache resources

Cache location

This field contains either the path or the DLName of the Cache's location.

As the goal of the Cache is to optimize the traffic between the data repository and the process memory, it is not possible to define the directory path on a network drive. When cache is activated, this path can be modified by user.

Only local, existing and valid paths can be entered, otherwise an error message is displayed and the last valid path remains.

The cache directory is created, as needed. Default locations for the Persistent cache are:

  • on Windows: CSIDL_LOCAL_APPDATA\DassaultSystemes\ where CSIDL_LOCAL_APPDATA is recognized only in the user context. A typical path is C:\Users\username\AppData\Local

  • On LINUX and UNIX: $HOME\

    When a user path is specified, a sub-directory PLM_CACHE_<ReleaseNumber> is created under the specified cache location path, as the root directory for the downloaded streams storage tree.

If you click on , all streams except streams used by the session or locked by the LocalSave functionality, are deleted.

After choosing the Cache location, restart the application to take current change into account.

Streams cache: Maximum size in MB


The maximum cache size defines the maximum disk size allowed by user for the Streams cache.

When cache size exceeds the maximum authorized size, it is decreased to its half maximum size.

  • The default value is 1000Mb.
  • The minimum value is 10Mb.
  • The cache maximum size may be then overridden depending on streams lock and other removal priority factors.
Streams cache: Disk Memory use

When selected, this option indicates the current size of the Persistence Cache.

You do not need to restart your application after deleting the streams to see the change.

The initial value is 0Kb. 0 means that there is no data yet in cache for a new first session. For subsequent sessions, the disk space currently used by the cache is displayed.

Check cache coherency

When selected, this option activates a check at the beginning of each session to avoid issues linked to possible persistence cache inconsistency: the index of the persistence cache is scanned and the presence of every listed file is checked on the persistence cache local disk.

Metadata cache


This cache contains the PLM attribute values for each bos/rels.

The Max entries indicates the number of bos/rels (BusinessObject and RelationshipType) that are stored in the PLM data cache. The updated data is systematically stored in this cache and not on the server. The server load is consequently reduced to a minimum.

 

See Also
More help on this topic