Changes between Version 104 and Version 105 of PetascopeUserGuide


Ignore:
Timestamp:
Dec 30, 2015 3:19:07 PM (21 months ago)
Author:
pbaumann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PetascopeUserGuide

    v104 v105  
    3535 * For the handling of '''time''' series see [PetascopeTimeHandling this page].
    3636 * For insights on dimensionless '''index''' coordinate reference systems see [IndexCrss this page].
    37 
    38 == Caches ==
    39 
    40 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.
    41 
    42 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.
    43 
    44 Thanks 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.
    4537
    4638== Static tables ==
     
    692684 * ...
    693685
     686== Caches ==
     687
     688Petascope 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.
     689
     690It 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.
     691
     692Thanks 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.
     693
    694694== Tickets reporting deviations from standards ==
    695695Tickets reporting deviations should be tagged with the keyword "deviation" so they can get listed here and assessed for documentation.