3 ms·
It's not underlined in the article, but for anyone who didn't follow this issue while it peaked: the root cause was (still is?) a notable delay when contacting
by daneel_w 4y ago
It's not underlined in the article, but for anyone who didn't follow this issue while it peaked: the root cause was (still is?) a notable delay when contacting Apple's servers to enquire about fingerprints of an executable that was about to launch, for anti-malware purposes. There were loads of reports that the problem disappeared entirely by just disabling Internet access, an obviously unideal solution.
- Cthulhu_ 4y agoThe article is a bit misleading I think, since the check only happens on startup; a lot of people won't start up new apps on the regular. Developers probably do though.
- daneel_w 4y agoAnother observation that went missing from the discussions around this problem is that it pans out differently (worse) for people in North America than it does for European users. Apple's various CDNs are far from equally encumbered. Reports from North American users held numbers well beyond those reported by European users. For me here in Sweden the problem was at its peak no more than a lesser annoyance. Not once did I observe anything near the dredging 5-30 second delays that North American users reported, and the recurring 2-3 seconds long system freezes never manifested for me at all.