Google storage bucket plugin #121
Merged
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
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.
Inspired by Ignacio's BigTable plugin, I added a plugin for Google Storage. While the latency to objects in Google's storage buckets is much worse than BigTable, this plugin might be useful in situations when batch access to cheaper storage is required.
It is unclear whether it might just be better to have a single DVID with an embedded leveldb on a Google VM for many use cases. Assuming the latency is much better with an embedded leveldb on a VM, total read/write throughput might be superior to small cluster deployments using google buckets. However, the cost of persistent disks is slightly more than google bucket storage and persistent disks appear to have a 10TB limit. Furthermore, in some batch operations, such as image segmentation, the read/write throughput requirements are insignificant compared to the compute required.
This plugin is mostly disjoint from the rest of DVID. The plugin has been tested by exercising part of the DVID API manually. Formal testing still needs to be added.
Documentation on how to use the plugin is in the DVID wiki.