News for hackers. Stuff that matters.
Re:Amazon Elastic File System on Kubernetes by nemothekid on Wednesday February 14, 2018 @05:18PM (#16380030)
Like others have mentioned, EFS has it's own surprises. To get decent performance, you will see a lot of recommendations to store at least 1TiB on EFS to get decent performance (so if your working set is 100MiB, store, you need 999GiB of garbage), meaning you will spend $300/mo for capacity you don't need.
Re:Amazon Elastic File System on Kubernetes by notyourwork on Wednesday February 14, 2018 @05:25PM (#16380071)
Can you elaborate on why storing more data would fix your issues? I assume its because it moves you to a different tier but the claim seems strange for those unfamiliar with EFS.
Re:Amazon Elastic File System on Kubernetes by nemothekid on Wednesday February 14, 2018 @05:55PM (#16380317)
You are right - the amount of throughput you get is based on how much data you store. Whats unintuitive about EFS is you get an "allotment" of throughput. Lets say you have 100MiB of data, you would get 100 MiB of throughput (example numbers). So you read that 100MiB of data, really quickly, and then the next time you read it, EFS is as slow as molasses.

So lets say you are using EFS for application deploys. Your application might only be 50MiB, but if you are doing multiple deploys a day, you might find that your deploy time shoots through the rough after 20 deploys. You find out that you have used up your "EFS" credits and the only way to get more is to store more data on EFS. I believe the first tier is at 100GiB.

Re:Amazon Elastic File System on Kubernetes by longwave on Wednesday February 14, 2018 @05:55PM (#16380311)
Throughput is proportional to total data size - 50Mb/sec per Tb - and burst capacity above this is severely restricted until you have at least 1Tb of data.