11–20 of 52 posts
What 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?
Does this mean Atlassian products will be quick(er)? Perhaps they should concentrate there if not.
It's not by Atlassian...
What 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?
It appears to pool RAM from many servers. That would allow pool sizes larger than what fits in a single physical server.
Earlier quoted context omitted.
> The RAMCloud project is based in the Department of Computer Science at Stanford University. It's not by Atlassian...
Sure, but the URL is for Atlassian.net
Is 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.
How does this work if someone is doing multiple sequential writes? Doesn't backup-ing to disk take a lot longer than writing to _RAM_ meaning some writes could get lost?
Is 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.
Did you use it in production ?