1.4.5. PARTapplicationServer
installation/configuration 1.4.5.4. Caching methods
for data storage and operation
|  |
| Prev | Next |
Caching is basically recommended. In case of doubt make use of CADENAS consulting. Otherwise please regard the default settings.
The following table gives an overview on the different caching methods.
| Cache Server | RFS (Remote Filesystem Caching) | ||
|
The PARTapplicationServer caches data directly from CADENAS_DATA. Requested data is cached and distributed if requested again. Also see Section 1.4.5.9.1.9, “ Caching index files of $CADENAS_DATA on PARTapplicationServer ”. |
Remote location caches data which have been requested from the central PARTapplicationServer and distributes it from cache when requested again. |
Client stores all data which have been requested by him and so saves a further request to PARTapplicationServer or CADENAS_DATA. | |
|
No direct access on CADENAS_DATA required. No replication of CADENAS_DATA to remote locations required. Indexes don't have to be locked for catalog installation. Cache fetches update once performed on CADENAS_DATA. |
No replication to the remote locations required. Performance on data in cache very good, if modelers use the same data. |
No direct access on CADENAS_DATA required. No replication of CADENAS_DATA to remote locations required. |