ProTrack Warehouse uses a method of caching in order to optimize performance when computing shortest-path travel calculations. A dual-stage caching methodology has been implemented as of ProTrack Warehouse version 7.3, which first caches node-to-node travel, and then caches travel routes between unique pairs of locations. Once both stages are completed for a pair of locations, that particular pairing is considered to be "fully “fully cached." ”
ProTrack Warehouse utilizes two methods in order to build the cache. First a node-to-node cache is ALWAYS primed (ahead of the time that it is actually needed during standards calculation). Additionally, some degree of location-to-location cache can be primed. The process of building these two pre-caches is referred to as "priming “priming the cache." ” Secondly, as travel time is calculated between two locations, the shortest path is cached "on“on-the-fly" fly” for location pairing without a pre-existing cache.
...
Node caching and location caching can both be independently "primed" “primed” ahead of time before standards are being calculated. This results in a huge performance gain when calculating standards involving travel.
"Priming" “Priming” the cache means that there will be a "history" “history” generated of travel combinations between two locations and nodes before travel actually occurs between those locations in the live production environment.
...
image | ||||
---|---|---|---|---|
| ||||
...
Clicking on the Generate Node Cache button creates an entry in Scheduled Requests. The progress of the task can be monitored on the Monitor > Scheduled Request screen.
image | ||||
---|---|---|---|---|
| ||||
Contained in the right box are all options for generating Location Cache. The options that the user must specify are similar to those for Node Cache:
Clicking on the Generate Location Cache button creates an entry in Scheduled Requests. The progress of the task can be monitored on the Monitor > Scheduled Request screen.
image | ||||
---|---|---|---|---|
| ||||
Whether or not the two caches need to be recalculated depends on what was changed. Here are the different change scenarios and requirements:1.
...
Info | ||
---|---|---|
| ||
|