iphone 3.0 Update + Slow Backup Process - Why Design the Backup like that??
I'm hoping one of Apple's staff will respond to this post. I'm sorry it is long and rambling, but the interesting stuff is at the bottom, so stay with me...please. And yes I'm a bit frustrated because my lovely iPhone has now been tied up for 9+ hours... not a good user experience.
This post is really about the backup process itunes initiates whenever I attempt to sync my iphone. I've never yet seen itunes get to the end of the backup. After the first 6 hours I get board and stop the process. iTunes is installed on Vista 64.
Well last night I downloaded Itunes 3.0 update and kicked off the upgrade process in iTunes. All was well (and at the time of writing I guess still is). The backup kicked off at 21:54 on 17 June. It is now 8:11 on 18 June and the backup is still going. The progress bar is still increasing (no x available to cancel) and I've the folder location in open in Windows Explorer. Last time I looked the backup folder contained some 21,000+ files. 1st file plist.status was written at 21:54. iTunes backup is still posting files to this folder!!!
Using some pretty basic Windows Tools to see what was going on I found out the following.
Apple backup uses 3 processes, one a Windows Service called AppleMobileDeviceService.exe. Another process called AppleMobileDeviceHelper.exe and AppleMobileBackup.exe. They are all network enabled. AppleMobileDeviceService is the hub and listens on port 27015. It 'talks' to the other two services on various & variable port range in the TCP/IP stack.
Using Windows Performance Monitor I can see that the TCP conversation going on between AppleMobileDeviceService & AppleMobileBackup is running at between 9,000,000 Bytes a Minute (min) and 14,000,000 Bytes a Minute (max). That is 1.2 Megabits per Second (min) & 1.86 Megabits per Second (max). That too me is very slow when the USB 2.0 interface its connected to has a capacity of up to 480Mbits per second.
It occurs to me that the methodolgy Apple's Devs have chosen for the backup process appears to be incredibly flawed.
I can't test whether the backup is also using compression, although I hope so because of the 21,000+ files (and climbing) in the backup folder to date they only add up to 200MBytes. My iPhone has 7 of its 8GBytes used, so I could be in for a very long haul before I get my updated iPhone 3.0 software.
Apple, please this isn't a dig, I know I've got Windows on the desk (its my day job)but I love my iPhone and AppleTV.
Can you ask your Devs to explain why they chose to use such a slow methodology to underpin the iPhone backup service. Or, is it that the potential high speed backup that is possibel over TCP/IP is just very broken?
Lastly, when is Apple going to fix this, because this backup thing is very broken and giving your customers an incredibly poor user experience.
Anyway, hope this was a little bit informative for those suffering the same trying to get their iPhone upgraded to 3.0.
Thanks
Pete.
handcrafted+dell, w7+vista+2008