Rosyna Keller on Twitter: "@danielpunkass @mjtsai There are even different throttles used depending on if the device is seen as an SSD or not an SSD by the system!"

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

Daniel Jalkut ‏@danielpunkass Mar 17

@mjtsai The Time Machine "low priority" thing is interesting. At first blush, I think it affects restore, too? It’s always IMPOSSIBLY slow…
Daniel Jalkut ‏@danielpunkass Mar 17

@mjtsai I always assumed it was a network latency thing, but it appears it was far more about the damned CPU priority. Ugh!
Michael Tsai ‏@mjtsai Mar 17

@danielpunkass Nope, Time Machine has always been much slower for local backups, too.
Rosyna Keller ‏@rosyna Mar 17

@mjtsai @danielpunkass I believe it's intentional, so actions after OS X updates remain responsive. Also affects Spotlight, cache rebuilding
Daniel Jalkut ‏@danielpunkass Mar 17

@rosyna @mjtsai They should at LEAST jack up CPU priority when in that focused restore browser.
1 like
Rosyna Keller ‏@rosyna Mar 17

@danielpunkass @mjtsai CPU isn't throttled. The bottleneck is disk I/O. (lowpri_throttle_enabled is an I/O throttle, not a CPU throttle)
Rosyna Keller ‏@rosyna Mar 17

@danielpunkass @mjtsai You can independently confirm it's an I/O throttle by looking at the source that uses it, http://www.opensource.apple.com/source/xnu/xnu-2422.1.72/bsd/miscfs/specfs/spec_vnops.c?txt …
1 retweet 1 like
Rosyna Keller ‏@rosyna Mar 17

@danielpunkass @mjtsai Throttling disk I/O has a side effect of lowering CPU use by reducing working set. But that's not the main goal.

‏@rosyna

@danielpunkass @mjtsai There are even different throttles used depending on if the device is seen as an SSD or not an SSD by the system!

6:27 PM - 17 Mar 2016

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.