Changes between Version 109 and Version 110 of PetascopeUserGuide


Ignore:
Timestamp:
Mar 22, 2017 7:22:46 PM (6 months ago)
Author:
pbaumann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PetascopeUserGuide

    v109 v110  
    3737== Caches ==
    3838
    39 Petascope currently keeps a few internal caches, especially for [SecoreUserGuide SECORE] CRS resources and responses: the gain is both on performance and on robustness against resolver's or network  problems. Caching information about CRSs is safe: CRSs can be considered static resources, they might not change for years, or never.
    40 
    41 It should be noted that even in case of a locally deployed resolver, still coverages can be configured to a CRS whose definition is provided by an external resolver.
     39Petascope currently keeps a few internal caches, especially for [SecoreUserGuide SECORE] CRS resources and responses: the gain is both on performance and on robustness against network latencies. Caching information about CRSs is safe as CRSs can be considered static resources - normally they do not change (and with the CRS versioning recently introduced by OGC a particular CRS version never will change indeed).
     40
     41It should be noted that even in case of a locally deployed resolver, still coverages can reference CRSs whose definitions are provided by external resolvers.
    4242
    4343Thanks to caches the network traffic for elaborate a request goes down to zero, so the performance gain is relevant: indeed you will observe slow responses on a newly deployed Petascope, but when caches start to get filled then response times get much shorter. It is suggested to run a WCS ''!GetCapabilities'' after a fresh new deployment, so that the CRS definitions of all the offered coverages are cached: after that single request, mainly almost all the CRS-related information has already been cached.