picklebase #638
Merged
picklebase #638
Conversation
This file contains 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
adamkendis
approved these changes
May 21, 2020
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.
The picklecache was a file-based replacement for Redis. Picklebase is essentially a file-based replacement for Postgres.
This code doesn't do anything unless the PICKLEBASE environment variable is set to 1, in which case all queries, except the pin-detail query, get their data from the filesystem instead of from the database. If the env var isn't set, queries go to the database as usual.
There are definitely some details to be ironed out here, but I'm just curious to see if it works first.
update: it looks like we have 273 gigs of storage in the /tmp filesystem:
So I moved all the files in there.
devbranchAny questions? See the getting started guide