RAMCloud Project
ramcloud.atlassian.net
RAMCloud Project
1–10 of 52 posts
Re: RAMCloud Project
#2How does it replicate all the data on disk or flash while maintaining the write latency of DRAM?
I'm thinking there must be a delay during which loss of power will result in loss of data that was acknowledged as written. Is this something that RAMCloud overcomes in a novel way, or is the answer simply that the data is replicated across many nodes?
How about the problem of raw bandwidth? If you keep sending writes to a node that exceeds the bandwidth of the persistent storage medium but is well within the capabilities of DRAM, the storage medium will never be able to catch up even if we allow a generous delay. Maybe this is a non-issue right now because you can't send more than a few dozen Gbps over the network anyway, and we just need to hope that flash performance will improve faster than 100GbE goes mainstream.
Re: RAMCloud Project
#3How does it replicate all the data on disk or flash while maintaining the write latency of DRAM? I'm thinking there must be a delay during which loss of power will result in loss of data that was acknowledged as written. Is this something that RAMCloud overcomes in a novel way, or is the answer simply that the data is replicated across many nodes? How about the problem of raw bandwidth? If you keep sending writes to…
Given the odds of these people inventing a huge solution to a hard problem in a publishing vacuum (I am not aware of papers coming out that fundamentally solve this, for example) I think it is pretty safe to assume it's subject to the same limitations all such systems are subject to. Loss of power leads to loss of data. Commonly mitigated as you already state.
Re: RAMCloud Project
#4How does it replicate all the data on disk or flash while maintaining the write latency of DRAM? I'm thinking there must be a delay during which loss of power will result in loss of data that was acknowledged as written. Is this something that RAMCloud overcomes in a novel way, or is the answer simply that the data is replicated across many nodes? How about the problem of raw bandwidth? If you keep sending writes to…
Given the odds of these people inventing a huge solution to a hard problem in a publishing vacuum (I am not aware of papers coming out that fundamentally solve this, for example) I think it is pretty safe to assume it's subject to the same limitations all such systems are subject to. Loss of power leads to loss of data. Commonly mitigated as you already state.
The Raft Consensus Algorithm (https://raft.github.io/) was born out of this project
Re: RAMCloud Project
#5Calling RAMCloud "new" seems a bit disingenuous since the first paper came out around 7 years ago.
Re: RAMCloud Project
#6How does it replicate all the data on disk or flash while maintaining the write latency of DRAM? I'm thinking there must be a delay during which loss of power will result in loss of data that was acknowledged as written. Is this something that RAMCloud overcomes in a novel way, or is the answer simply that the data is replicated across many nodes? How about the problem of raw bandwidth? If you keep sending writes to…
Seems reasonable when the date on the OP is 9 years ago.
Re: RAMCloud Project
#7Calling RAMCloud "new" seems a bit disingenuous since the first paper came out around 7 years ago. https://dl.acm.org/citation.cfm?id=2043560
It's not new. These wiki/project pages have years of history and haven't been updated.
Re: RAMCloud Project
#8Is this still maintained? It's a really cool project, it's just so insanely fast.
I once implemented a MariaDB storage engine that used RAMCloud for storage, and it was an eye-opening experience. With blazingly fast reads and writes, latency was the number one performance issue for us.
Re: RAMCloud Project
#9What would be the difference between this and an SSD-based keystore and an instance of memcached with as much RAM as was necessary to hold the whole dataset?
Re: RAMCloud Project
#10Does this mean Atlassian products will be quick(er)? Perhaps they should concentrate there if not.