Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ### mod_tile
- #LoadTileConfigFile /home/project/o/s/m/osm/renderd/etc/renderd.conf
- LoadTileConfigFile /home/project/o/s/m/osm/tirex/etc/tirex/mod_tile.conf
- # Timeout before giving for a tile to be rendered
- ModTileRequestTimeout 0
- # Timeout before giving up for a tile to be rendered that is otherwise missing
- ModTileMissingRequestTimeout 5
- # If tile is out of date, don't re-render it if past this load threshold (users gets old tile)
- ModTileMaxLoadOld 4
- # If tile is missing, don't render it if past this load threshold (user gets 404 error)
- ModTileMaxLoadMissing 30
- # Socket where we connect to the rendering daemon
- #ModTileRenderdSocketName /home/project/o/s/m/osm/renderd/var/renderd.sock
- ModTileRenderdSocketName /home/project/o/s/m/osm/tirex/var/run/tirex.sock
- ## Caching is both important to reduce the load and bandwidth of the server, as
- ## well as reduce the load time for the user. The site loads fastest if tiles can be
- ## taken from the users browser cache and no round trip through the internet is needed.
- ## With minutely or hourly updates, however there is a trade-off between cacheability
- ## and freshness. As one can't predict the future, these are only heuristics, that
- ## need tuning.
- ## If there is a known update schedule such as only using weekly planet dumps to update the db,
- ## this can also be taken into account through the constant PLANET_INTERVAL in render_config.h
- ## but requires a recompile of mod_tile
- ## The values in this sample configuration are not the same as the defaults
- ## that apply if the config settings are left out. The defaults are more conservative
- ## The values in this sample configuration are not the same as the defaults
- ## that apply if the config settings are left out. The defaults are more conservative
- ## and disable most of the heuristics.
- # Upper bound on the length a tile will be set cacheable, which takes
- # precedence over other settings of cacheing
- ModTileCacheDurationMax 604800
- # Sets the time tiles can be cached for that are known to by outdated and have been
- # sent to renderd to be rerendered. This should be set to a value corresponding
- # roughly to how long it will take renderd to get through its queue. There is an additional
- # fuzz factor on top of this to not have all tiles expire at the same time
- ModTileCacheDurationDirty 900
- # Specify the minimum time mod_tile will set the cache expiry to for fresh tiles. There
- # is an additional fuzz factor of between 0 and 3 hours on top of this.
- ModTileCacheDurationMinimum 10800
- # Lower zoom levels are less likely to change noticeable, so these could be cached for longer
- # without users noticing much.
- # The heuristic offers three levels of zoom, Low, Medium and High, for which different minimum
- # cacheing times can be specified.
- #Specify the zoom level below which Medium starts and the time in seconds for which they can be cached
- ModTileCacheDurationMediumZoom 13 86400
- #Specify the zoom level below which Low starts and the time in seconds for which they can be cached
- ModTileCacheDurationLowZoom 9 518400
- # A further heuristic to determine cacheing times is when was the last time a tile has changed.
- # If it hasn't changed for a while, it is less likely to change in the immediate future, so the
- # tiles can be cached for longer.
- # For example, if the factor is 0.20 and the tile hasn't changed in the last 5 days, it can be cached
- # for up to one day without having to re-validate.
- ModTileCacheLastModifiedFactor 0.20
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement