3 ms·
Great guide. I've been using AWS since there were only a handful of services and it's become increasingly hard to keep up with all the additional ones that have
by aidos 10y ago
Great guide. I've been using AWS since there were only a handful of services and it's become increasingly hard to keep up with all the additional ones that have been added in the last few years.
EFS had completely passed me by. Does anyone have experience with it? I'm wondering what it would be like to use for Whisper / Graphite (just on a single machine). I'm less interested with concurrent access and more interested in not having to resize drives as data grows / overprovision drives all the time.
- inyourtenement 10y agoAs I recall it's significantly more expensive than EBS, which kept me away. I've had a few use cases come up where shared access would be nice, but I was always able to use objects in s3 instead, which is far cheaper.
- aidos 10y agoIt's about 3x the price of EBS by the looks, but then again, I probably run 10x the size EBS drive required so I don't need to deal with scaling it often...!
- ljosa 10y agoThe latency is higher than I had hoped. I wrote 10,000 files with 10 kb in each. It took 23 ms per file on average. Then I read them back. That took 8 ms per file on average. That's way too much for the use case I was contemplating, so I didn't investigate further.
- aidos 10y agoIt definitely _felt_ a bit slow rysncing to it last night. In the Whisper use-case, there are a ton of small appends to do every minute - so that could be an issue. I'm going to set up a machine with a linux 4 kernel today to try it on (as that's what they recommend, along with async mode).