Guest User

Untitled

a guest
Jan 23rd, 2014
185
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. ### mod_tile
  2. #LoadTileConfigFile /home/project/o/s/m/osm/renderd/etc/renderd.conf
  3. LoadTileConfigFile /home/project/o/s/m/osm/tirex/etc/tirex/mod_tile.conf
  4. # Timeout before giving for a tile to be rendered
  5. ModTileRequestTimeout 0
  6. # Timeout before giving up for a tile to be rendered that is otherwise missing
  7. ModTileMissingRequestTimeout 5
  8. # If tile is out of date, don't re-render it if past this load threshold (users gets old tile)
  9. ModTileMaxLoadOld 4
  10. # If tile is missing, don't render it if past this load threshold (user gets 404 error)
  11. ModTileMaxLoadMissing 30
  12. # Socket where we connect to the rendering daemon
  13. #ModTileRenderdSocketName /home/project/o/s/m/osm/renderd/var/renderd.sock
  14. ModTileRenderdSocketName /home/project/o/s/m/osm/tirex/var/run/tirex.sock
  15.  
  16. ## Caching is both important to reduce the load and bandwidth of the server, as
  17. ## well as reduce the load time for the user. The site loads fastest if tiles can be
  18. ## taken from the users browser cache and no round trip through the internet is needed.
  19. ## With minutely or hourly updates, however there is a trade-off between cacheability
  20. ## and freshness. As one can't predict the future, these are only heuristics, that
  21. ## need tuning.
  22. ## If there is a known update schedule such as only using weekly planet dumps to update the db,
  23. ## this can also be taken into account through the constant PLANET_INTERVAL in render_config.h
  24. ## but requires a recompile of mod_tile
  25.  
  26. ## The values in this sample configuration are not the same as the defaults
  27. ## that apply if the config settings are left out. The defaults are more conservative
  28. ## The values in this sample configuration are not the same as the defaults
  29. ## that apply if the config settings are left out. The defaults are more conservative
  30. ## and disable most of the heuristics.
  31.  
  32. # Upper bound on the length a tile will be set cacheable, which takes
  33. # precedence over other settings of cacheing
  34. ModTileCacheDurationMax 604800
  35.  
  36. # Sets the time tiles can be cached for that are known to by outdated and have been
  37. # sent to renderd to be rerendered. This should be set to a value corresponding
  38. # roughly to how long it will take renderd to get through its queue. There is an additional
  39. # fuzz factor on top of this to not have all tiles expire at the same time
  40. ModTileCacheDurationDirty 900
  41.  
  42. # Specify the minimum time mod_tile will set the cache expiry to for fresh tiles. There
  43. # is an additional fuzz factor of between 0 and 3 hours on top of this.
  44. ModTileCacheDurationMinimum 10800
  45.  
  46. # Lower zoom levels are less likely to change noticeable, so these could be cached for longer
  47. # without users noticing much.
  48. # The heuristic offers three levels of zoom, Low, Medium and High, for which different minimum
  49. # cacheing times can be specified.
  50.  
  51. #Specify the zoom level below which Medium starts and the time in seconds for which they can be cached
  52. ModTileCacheDurationMediumZoom 13 86400
  53.  
  54. #Specify the zoom level below which Low starts and the time in seconds for which they can be cached
  55. ModTileCacheDurationLowZoom 9 518400
  56.  
  57. # A further heuristic to determine cacheing times is when was the last time a tile has changed.
  58. # If it hasn't changed for a while, it is less likely to change in the immediate future, so the
  59. # tiles can be cached for longer.
  60. # For example, if the factor is 0.20 and the tile hasn't changed in the last 5 days, it can be cached
  61. # for up to one day without having to re-validate.
  62. ModTileCacheLastModifiedFactor 0.20
RAW Paste Data