Our 3D CAD supplier models have been moved to 3Dfindit.com, the new visual search engine for 3D CAD, CAE & BIM models.
You can log in there with your existing account of this site.
The content remains free of charge.
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.
SQUID | 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.3.9.9.3.7, “ 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. Also see Section 1.3.9.9.2.4, “Caching on client side or at secondary locations ”. |
Client stores all data which have been requested by him and so saves a further request to PARTapplicationServer or CADENAS_DATA. Also see Section 1.3.9.9.2.4, “Caching on client side or at secondary locations ”. |
|
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. |