Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My understanding is that EBS has some heuristics for deciding whether to keep data cached; an AMI which has a cached snapshot as its root disk will boot much faster than an AMI where all the data needs to be pulled from S3.


Some huge customer chunked their data into 5GB pieces so now there's a "if size == 5GB" in the cache code.


Maybe, but I don't think that would explain 8 GB also being fast while 6 GB is slow?


Yeah, I found that pretty unintuitive when I read it. How did you find 8GB worked? Trial and error?


Customer started using 8GB chunks /s


What's the smallest size for which those heuristics keep the snapshot cached?

(I'm currently using 1GB snapshots, because my actual disk image is a tiny fraction of that size. But if bumping that to 2GB or 4GB would make it faster, that's a small price to pay.)


I believe 1 GB is also fast.


Thanks, that helps to hear!

Do you have any other wisdom regarding mysterious reasons for fast or slow booting? EC2's boot process is deeply opaque, and any insight at all is better than nothing.


Nothing comes to mind, but if you want to drop me an email I can walk you through some benchmarking.


At a guess, powers of 2 are fast?


5 is not a power of 2. ;-)


Gotta admit it's pretty close though.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: