Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

iOS 6.0 Causes CDN Overages

labs.prx.org

Post reply on HN
Print view View original

91–96 of 96 posts

Re: iOS 6.0 Causes CDN Overages

#91

Post by noinput »

donavanm wrote: post #60
noinput wrote: post #17

Same here, noticed a huge spike in bandwidth for my startup's shows hosted on CloudFront. 206 responses are flooding my logs and I moved everything off of CloudFront for my users to triage the cost. This breakdown explains it all: http://cl.ly/image/2H3u3u2O333g Talk about a pain, not to mention the 10x bill from Amazon that came as a surprise.

"I moved everything off of CloudFront for my users to triage the cost." Can you explain more? Was there some cloudfront behavior exacerbating the issue? AFAIK this is just a client (mis)using range requests and CloudFront replying as requested.

You are correct and I should have wrote that note differently. I moved some high traffic files to some endpoints I have where bandwidth isn't a concern to change the formula a bit (primary) and the rest are back to using basic S3 for now. The bandwidth is still being consumed, however now it's easier on the wallet.

After looking more closely at the differences for pricing between S3/CloudFront I realize it's appears cheaper to be on CloudFront. I assumed wrong that CloudFront data-out was billed in addition to S3 because of the way it's notated on the usage page ("AWS Data Transfer (excluding Amazon CloudFront)"). To prove it I ran two reports on CF (left) and S3 (right): http://cl.ly/image/0q0y3u2X0g1a and you can tell where I made the change, as well data is only counted on the service in question and not on both.

Can anyone else confirm the above?

Re: iOS 6.0 Causes CDN Overages

#92

Post by malyk »

burriko wrote: post #77
malyk wrote: post #56

Earlier quoted context omitted.

Last month I moved and didn't have an ISP at home for the first 3 weeks or so. I set up tethering on my phone and a 5GB data plan. Yesterday I got a notice that I was over my data limit. I haven't done a whole lot of web surfing in the new house, but I have listened to a ton of podcasts using the Podcast app which I have never done before. So if I just blew through 5 GB of data in 2ish weeks and the only thing differ…

Netflix's 720p streams use 2.3GB/hour, which would certainly put you over 5GB. I'm not sure about their lower quality streams though.

Hmmm, maybe that is it then. I'd be surprised if I was getting that data rate on my 3G connection (iphone 4s, at&t).

I'm still shocked it happened so quickly though. I guess 5 GB isn't what it used to be! ;)

Re: iOS 6.0 Causes CDN Overages

#93

Post by mkr-hn »

pretoriusB wrote: post #85
mkr-hn wrote: post #83

Earlier quoted context omitted.

The only thing you could infer from that is that you're not a bad enough poster to warrant downvotes.

Not really. It's a sure sign that you are hell-banned. I mean, we can check statistically, and I bet we would find that nobody stays at 1 point forever in all his comments. (And it's also upvotes you won't be getting).

I can't be the only one who upvotes good comments from hellbanned accounts in the hopes that the vote will have some impact.

Re: iOS 6.0 Causes CDN Overages

#94

Post by gurkendoktor »

Ensorceled wrote: post #90
gurkendoktor wrote: post #81

Earlier quoted context omitted.

How do you know that Forstall was the person advocating a yearly OS upgrade cycle? It seems just as likely to me that this rigid schedule was forced onto him and he couldn't deliver. Things like OS X Lion (a huge change under the hood) and the Maps places database just aren't things that can be built to a deadline.

Well, a mess was shipped and he was the guy in charge. So I'm assuming he was the guy responsible. If a mess really was forced upon him he should have resigned instead of sticking around to ship the mess. I have in that exact same situation, "This will not be associated with me, I'm out"

Now you are talking about saving face, not about saving iOS. Maybe he was the best guy for the job and he still couldn't do it.

Re: iOS 6.0 Causes CDN Overages

#95

Post by donavanm »

noinput wrote: post #91
donavanm wrote: post #60

Earlier quoted context omitted.

"I moved everything off of CloudFront for my users to triage the cost." Can you explain more? Was there some cloudfront behavior exacerbating the issue? AFAIK this is just a client (mis)using range requests and CloudFront replying as requested.

You are correct and I should have wrote that note differently. I moved some high traffic files to some endpoints I have where bandwidth isn't a concern to change the formula a bit (primary) and the rest are back to using basic S3 for now. The bandwidth is still being consumed, however now it's easier on the wallet. After looking more closely at the differences for pricing between S3/CloudFront I realize it's appears…

Yeah, that's a bit confusing. Using Cloudfront with an S3 bucket is double billed, the first time. On a cache miss Cloudfront pulls the object from S3 and serves it to the client. S3 bills the regular data transfer out. Cloudfront then bills the regular data out to client rate.

On subsequent requests, cloudfront cache hits, you're only billed by Cloudfront. Cloudfront request + byte rates are cheaper than S3 in Us-east-1, IIRC. So on popular or high ttl objects it's cheaper to serve through Cloudfront. On low ttl or low rps, like a few requests per day, it's cheaper to use standalone s3.

The same origin + CDN vs CDN Hit math applies to EC2 as well. I do wish the billing was clearer in these scenarios.

Re: iOS 6.0 Causes CDN Overages

#96

Post by noinput »

donavanm wrote: post #95
noinput wrote: post #91

Earlier quoted context omitted.

You are correct and I should have wrote that note differently. I moved some high traffic files to some endpoints I have where bandwidth isn't a concern to change the formula a bit (primary) and the rest are back to using basic S3 for now. The bandwidth is still being consumed, however now it's easier on the wallet. After looking more closely at the differences for pricing between S3/CloudFront I realize it's appears…

Yeah, that's a bit confusing. Using Cloudfront with an S3 bucket is double billed, the first time. On a cache miss Cloudfront pulls the object from S3 and serves it to the client. S3 bills the regular data transfer out. Cloudfront then bills the regular data out to client rate. On subsequent requests, cloudfront cache hits, you're only billed by Cloudfront. Cloudfront request + byte rates are cheaper than S3 in Us-ea…

Thank you so much for breaking that down.
Post reply on HN