Add more cache configuration options. #601
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added
cache_tilesource_memory_portion
andcache_tilesource_maximum
config options. The number of tile sources that are caches is the smallest of (a) the number of available file handles divided by a factor and reduced by a constant, (b) the available memory divided by the portion (default 8) and the expected size of the largest tile source, (c) the cache maximum value. Before, the portion was always 8 and there was no way to specify a maximum value.This can be applied in girder, for instance via the
[large_image]
section of the config file with something like::