I would hazard a guess that nearly all large scale use cases are negotiating those prices down quite a bit.

Keep reading - AWS latency was too high so the benchmark was run on some bare Dell hardware.

Call the credit card company and dispute the charges. Also, block any further charges if you can. Nothing gets people's attention like messing with their cash flow.

The downside is that the account will likely never be opened back up if a charge is disputed, and any future accounts could also be linked and auto-closed. Of course, if it's been closed for two weeks already, that's likely a moot point.

Thanks for the recommendation!

Fantastic article. I noticed a couple of TODO's around, though. Does this hint at a second installment? :)

If I need it for work at some point :-) Not in forseeable future :-( But you can send PRs or fork it: https://github.com/cirosantilli/cirosantilli.github.io/blob/...

Sure, but that ruins the fun :)

Thanks for letting me know, I'll see if I can fix it. If I could trouble you to do so, can you provide a screenshot?

I'm not the OP, but I have an iPad too, and I can provide screenshots.

http://instantshare.virtivia.com:27080/1eikl92n5jtyc.PNG - default view

http://instantshare.virtivia.com:27080/o1wn6nbthvuu.PNG - after zooming in unsuccessfully, OR just scrolling to the right

http://instantshare.virtivia.com:27080/eiw3z2u1n52h.PNG - fully zoomed out

http://instantshare.virtivia.com:27080/1jsmbx8km815h.PNG - the culprit causing this, a long URL which isn't being wrapped by your CSS rules

To be honest, the same issue happens on desktop browsers, it's just not as noticeable because the default zoom kinda matches what you'd expect. But you can still scroll to the side, in a desktop browser. See:

http://instantshare.virtivia.com:27080/b69zdjyzbvfo.png

I think the CSS fix can be something like this:

    word-wrap: break-word;

http://instantshare.virtivia.com:27080/1l8rbeisu9a2a.png

However, different browsers behave differently™, so you may need to also add:

    word-wrap: break-word;
    white-space: pre-wrap;

To make it work in Firefox (but you might need to adjust other things, also play with word-break CSS property, and test in all browsers). I've dealt with this previously at https://github.com/shurcooL/play/issues/4 and other places that deal with displaying user generated content.

This was probably not explained well. The compilation failed with an error saying that I was basically trying to do something that was not allowed.

For your second question: I don't believe there is a way to use a separate assembler.

client-side compression works out better for a couple of reasons:

1. You use less bandwidth in/out of the box. This matters in AWS because your bandwidth is (relatively) limited.

2. Your CPU usage to (de)compress is distributed over a larger fleet. The clients spend the CPU time, not the cache servers.

Yeah it absolutely is. In fact, there's been tons of large improvements as of late, with more coming.

Somewhat disappointing. It's just a long ad for nested.