6 ms·
I/O - It’s not easy to run Riak on AWS. It loves I/O. To be fair, they say this loud and clear so that’s my problem. We originally tried fancy EBS setup to
by joevandyk 15y ago
I/O - It’s not easy to run Riak on AWS. It loves I/O. To be fair, they say this loud and clear so that’s my problem. We originally tried fancy EBS setup to speed it up and make it persistant. In the end we ditched all that and went ephemeral. It was dramatically more stable for us overall.
If you're running any type of a database or service on EC2 where latency is an issue, you should be using ephemeral/instance storage. Not EBS.
- count 15y agoIf you're going to run Riak on AWS, why not just use AWS S3 service, which is the Dynamo that Riak is based on?
- deleted 15y ago[deleted]
- sorenbs 15y agoBecause s3 has latencies an order of magnitude higher than a local riak. This is especially important if you have many unparallizable requests.
- bretthoerner 15y agoRiak offers a lot more than the plain HTTP key/value that is S3.