add memcache service for large image caching#1599
Open
BryonLewis wants to merge 2 commits intomainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Without memcache girder-large-image uses python to cache data. This could be large especially if you are using docker
--scale girder=8. Large Image has the capability to automatically user memcache if it is located locally to the server (127.0.0.1:6379)https://github.com/search?q=repo%3Agirder%2Flarge_image%20memcache&type=code
https://github.com/girder/large_image/blob/9561be5f70f43c92a1d9afb5505e5a9fee755e79/docs/config_options.rst#L41
Per the documentation: adding the environment variables to force it to use memcache and to point it to the internal docker network name of 'memcached' should work for configuring memcache as the caching mechanism for large images instead of python.