Page History

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.

...

1. Location is added to a pre-existing Segment: no change to either cache is required.
2. Location is added to a newly imported Segment: additional node cache may be required. It is not necessary to delete existing node cache, simply regenerate it for the affected floor and automatically create any node cache that is missing due to the recent import of Segments.
   
   

   Info
   title Info
   This additional cache will only be required if option 3 in the Node Cache generation was set to 'Yes'‘Yes’. If it was set to 'No'‘No’, then all possible Node Cachings would have been generated in the first place so nothing could be missing.

   
   
3. Location is moved or deleted: location cache must be deleted.
   1. Any changes that result in regenerating Nodes: both caches must be deleted for the affected floor(s). This may result from an Aisle Path or Travel Path being added or deleted.
4. Additions, deletions, or modifications to Segments have no direct impact on either cache.