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

41–50 of 96 posts

Re: iOS 6.0 Causes CDN Overages

#41

Post by publicfig »

nikatwork wrote: post #34
publicfig wrote: post #21

Earlier quoted context omitted.

I think Apple has always had the tendency to make dumb mistakes, but I will say that I think reporting on it has changed. Remember all of the jokes about "It's not a bug, it's a feature" back when Jobs was there? Apple is by no means immune from mistakes and I don't think they ever were.

Exactly. The reality distortion field has collapsed and everyone is less willing to forgive mistakes. I mean come on, remember the MobileMe launch failure? That said, the famous Apple attention to detail does seem to be slipping, I sincerely hope this is just a transitional period and they tighten their game back up.

People also seem to forget how much of Apple's history was spent as a nearly faling tech company. Each little mistake is being reported to the point of saturation and while I think they're worth mentioning, every article seems to be a "beginning of the end" piece. As companies expand and begin to offer more and more products and services, it makes sense that their amount of bugs and mistakes would grow. When looking at gross amount of bugs and mistakes, you have to look at growth in offerings before major concern.

Re: iOS 6.0 Causes CDN Overages

#42

Post by fernandezpablo »

eridius wrote: post #40
fernandezpablo wrote: post #33

Makes you think twice about those graphics where iOS devices take a big piece of the pie of the "internet usage"

No it doesn't. Those aren't tracking bytes streaming over the internet, but rather web browsers visiting pages.

Yes it does.

Re: iOS 6.0 Causes CDN Overages

#43

Post by Ensorceled »

This is the reason Forstall has left the building, iOS 6 is a disaster:

    * Maps was not ready for prime time (so bad it required a public apology)
    * Podcast was not ready for prime time.
    * Passbook was not ready for prime time.
    * App store is a step backwards.
    * Battery and WIFI issues.
    * Soooo many bugs.
There are usually problems but this is the first time I've seen so much utter crap shipped including tons of minor bugs and issues (well Mobile Me was pretty bad :-)

I'm using Audible, Downcast and the built in Music app where I used to just use the Music app. iOS 6 was a huge step backwards for me.

Rather than waiting until it's ready (think copy/paste on iOS) Forstall was responsible for shipping a mess. Hopefully this will fix itself with new leadership.

Re: iOS 6.0 Causes CDN Overages

#44

Post by blinkingled »

danso wrote: post #22
dageshi wrote: post #9

Is it just me or are apple making more dumb mistakes lately? There's this and that ajax caching issue from a month or two ago. Perhaps I'm just having selective memory?

I dunno, how crummy the App Store has become is a perfect example of this. The App Store is one prominent way they make loads of money and build loyalty to the ecosystem, and yet it is a shitshow on IOS6...the responsiveness is as bad as I've seen on non-iOS software, but for me, the two really inexplicable failures are: 1. the use of modals to show individual apps on the iPad. So if you get to an app page and accide…

> the use of modals to show individual apps on the iPad

This bugged me a lot after iOS6 update. Also the small things such as when there are App Updates and badge shows up on the App Store icon, clicking it takes me to Featured Apps section - not updates as one would expect. On Android for instance, the update notification takes you directly to a screen allowing you to update as expected.

Re: iOS 6.0 Causes CDN Overages

#45

Post by rachelbythebay »

This just seems to be how they handle audio media. It's not even anything specific to podcasts. My own scanner stuff is just a web page, and it gets hit by this from time to time. Each call is a single file, it's static, and there's nothing funny going on with it. It looks like the playback stuff is jumping around in some attempt to figure out exactly what it is first. It seems like it would be far better if they always downloaded at least some reasonable quantity and then decided to bail out later if it seemed overly huge, but this is where we are.

To me, it feels like someone who's trying to be fancy and do things like seek() in a stream. Just because HTTP has progressed to the point where you can effectively do that with Range: requests doesn't mean it's a good idea. Offering seek() type behavior for a HTTP resource seems like a great way to get people to use it and not even realize what sort of messes they may be creating. Leaky abstractions, eh?

Here's just one example from last week. Note: the file is 7001 bytes. There's no reason for this insanity, and yet here it is.

    x.x.x.x - - [04/Nov/2012:16:02:47 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 2 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"
    x.x.x.x - - [04/Nov/2012:16:02:47 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 7001 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"
    x.x.x.x - - [04/Nov/2012:16:02:47 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 2 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"
    x.x.x.x - - [04/Nov/2012:16:02:47 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 2 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"
    x.x.x.x - - [04/Nov/2012:16:02:47 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 2 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"
    x.x.x.x - - [04/Nov/2012:16:02:48 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 7001 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"
    x.x.x.x - - [04/Nov/2012:16:02:48 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 7001 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"
    x.x.x.x - - [04/Nov/2012:16:02:48 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 2 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"
    x.x.x.x - - [04/Nov/2012:16:02:48 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 7001 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"
    x.x.x.x - - [04/Nov/2012:16:02:48 -0800] "GET /audio/16-1352070236.mp3 HTTP/1.1" 206 7001 "-" "AppleCoreMedia/1.0.0.10A403 (iPhone; U; CPU OS 6_0 like Mac OS X; en_us)" "scanner.rachelbythebay.com" "-"

Re: iOS 6.0 Causes CDN Overages

#46

Post by rachelbythebay »

untog wrote: post #31

This is where Apple's closed nature is very annoying. Assuming the article is correct, it was bug introduced in 6.0, and fixed in 6.0.1. So Apple knew about it, investigated it and published a fix. Yet they didn't tell anyone about it. Or the crippling effect this bug could have on their data allowances. Why not? Are they really that terrified of admitting to making a mistake?

This same behavior has been happening to me since before iOS 6 came out. I can show the same "206 storm" happening as far back as August of last year with iOS 4.3.5.

Re: iOS 6.0 Causes CDN Overages

#47

Post by randall »

rachelbythebay wrote: post #46
untog wrote: post #31

This is where Apple's closed nature is very annoying. Assuming the article is correct, it was bug introduced in 6.0, and fixed in 6.0.1. So Apple knew about it, investigated it and published a fix. Yet they didn't tell anyone about it. Or the crippling effect this bug could have on their data allowances. Why not? Are they really that terrified of admitting to making a mistake?

This same behavior has been happening to me since before iOS 6 came out. I can show the same "206 storm" happening as far back as August of last year with iOS 4.3.5.

I used to work at http://castfire.com/, and we've seen that similar issue from a LOT of iOS clients. Stats become increasingly difficult, because we saw one unique request bounce with upwards of 50+ 206s for similar / overlapping media... and then it bounced through a cell provider, to a WiFi network, and back, etc.

(we identified by redirecting all requests through a complex process of assigning an ID to them)

Hoping this is fixed. Podcast metrics are tricky, and this has been exacerbating the issue.

Re: iOS 6.0 Causes CDN Overages

#48

Post by mintplant »

riobard wrote: post #26

Hmm, so this explained my 3G data overage last month. I have 6GB/month of data, and usually I'd be using around only 700MB. But last month my iPhone 4S (running iOS 6.0) consumed nearly 8GB in total, resulted in quite some overage fee. Should I ask Apple for a refund for this? :|

Try your data carrier, rather than Apple.

Re: iOS 6.0 Causes CDN Overages

#49

Post by MaysonL »

danso wrote: post #22
dageshi wrote: post #9

Is it just me or are apple making more dumb mistakes lately? There's this and that ajax caching issue from a month or two ago. Perhaps I'm just having selective memory?

I dunno, how crummy the App Store has become is a perfect example of this. The App Store is one prominent way they make loads of money and build loyalty to the ecosystem, and yet it is a shitshow on IOS6...the responsiveness is as bad as I've seen on non-iOS software, but for me, the two really inexplicable failures are: 1. the use of modals to show individual apps on the iPad. So if you get to an app page and accide…

The thing that continually annoys, and occasionally infuriates me, is the f'ing no-button trackpad on the MBP: a dozen times a day my finger or thumb slips on the thing, just as I'm clicking, and it misses, or hits the wrong link.

Re: iOS 6.0 Causes CDN Overages

#50

Post by gigamike »

riobard wrote: post #26

Hmm, so this explained my 3G data overage last month. I have 6GB/month of data, and usually I'd be using around only 700MB. But last month my iPhone 4S (running iOS 6.0) consumed nearly 8GB in total, resulted in quite some overage fee. Should I ask Apple for a refund for this? :|

I had a similar experience. I normally consume 750-800 GB a month and on my first full month of iOS 6, Verizon said I consumed 8.89 GB. Luckily i'm grandfathered into an unlimited plan.
Post reply on HN