Zen and the Art of Migration to AP3

It would appear that Apple seriously underestimated the challenges that AP2 users might have moving to AP3.

After watching the sound and fury a bit, it appears to me that most of the problem is impatience with the massive task of converting old AP2 images to the new AP3 format.

After downloading the trial to a late 2009 Mini with 4 GB of RAM and the 500 GB disk I started to play.

First, I repaired permissions. Don't know if it helps, but it can't hurt.

Then I repaired and rebuilt my AP2 library.

Then I exported some sample projects - RAW, JPEG, and massive TIFFs. (Scanned slides of over 100 MB each)

First thing I found is that one of my projects would not export, not matter how many repairs I made. It always failed right at the end. The others had no problem. At first, AP3 would not import a project; I had to double click the project and then it sucked it right up. Interestingly, this problem went away with time, but only importing from the drop down window. From the "import " arrow/button it would never see projects out on disk.

Processing of each image in AP3 took beween five and ten seconds; sometimes more. Faces took a long time. (But this is hardly surprising.) Trying to do things while AP3 was processing was slow, as you might imagine, but once the 1000 or so images were moved over performance was better than AP2. I might note that I built the trial library on an external RAID O connected by FW800 - coupled with the 5000 rpm disk in the Mini, we are not talking about a blazingly fast disk system.

Found some bugs in printing, (would not remember paper size) but the results were fine and the new print module has more and better options.

Based on all of this (and since I have not yet received my boxed copy), I set out to import my AP2 library (managed) into AP3 - writing from the Mini internal disk to the RAID 0. (The RAID had lots of open space.) The library is about 1.65 GB with around 10,000 images in 275 projects.

Initial copy took just under three hours, with Faces off. Then began the dreading processing. At the five hour mark I have completed 2300 of 10000. I would note that the program seemed to hang for about an hour and a half at the 175 mark. Panic was setting in, but the Activity monitor showed continued disk I/O and CPU and memory usage fluctuations. AP3 took about 49% and the System took about 49% so, as you might imagine, everything else (including Safari to type this) is crawling.

Bottom line, however, is that there have been no crashes, etc. so far. I would thus venture a guess that some of the panic reported may be impatience.

Will try to post again when the import finishes or crashes.

As always - YMMV.

Good luck!

MBP, MacPro, Mac Mini, Mac OS X (10.6.2), Coolscan V ED, Vuescan

Posted on Feb 14, 2010 7:52 AM

Reply
2 replies

Feb 14, 2010 6:11 PM in response to DiploStrat

HI,

I like your Zen approach. In fact, why not take this to it's logical conclusion, and Zen-out until a patched, reliable version of Ap 3 is released?

We've all been waiting a long time for Ap 3, but survived, somehow, with Ap 2. It's professionally wise to avoid any x.0 release of software that you need for your living.

I am not aiming this comment at Diplostrat - but at any professional user.

Lots of anxious panics and chaos on the message boards! Yes, Apple seem to have taken the pie out of the oven a little too soon.

One side note - the main complaint is about the time taken to update previews et al. Now, I have just recovered a 1.5TB managed/referenced combination Ap 2 library from a Vault. I won't bore you with why I did this but:

Once that recovered Ap 2 library was opened, it required a further 12-18 hours to rebuild it's previews. And it hogged my 8 Core MacPro with 10GB ram to do so. This is with selected projects with "maintain previews" enabled, many disabled. And no faces - remember this is Ap 2.

So there's no slow down with Ap 3 - it's a process that just has to run it's course.

As for the memory leak - as I say, wait.


Ben

PS

If you must upgrade now my (2c) advice is:

1 Read this forum extensively

2 Get some fresh hard disk space (lots of it)

3 Export your projects, one by one, from Ap 2 (especially if you have a large library).

4 Backup your Ap 2 library, put that backup in a box, and place it somewhere safe and don't touch it again.

5 Run all diagnostic/repair/rebuild services on the Ap 2 library. (System wide repair permissions is an old wives tale and can do damage) prior to installing Ap 3.

6 Copy out all contents from ~/Library/Application support/Aperture and back them up.

7 Remove said above items from ~/Library/Application support/Aperture (you can experiment with putting them back later)

8 Remove Aperture (2) from the Applications folder (don't just rename it)

9 Install Aperture 3 from the downloaded version.

10 Boot (if on SL) in 32 bit kernel mode. 64 bit kernel mode affects device drivers, not aps.

11 Run Aperture 3 in 32 bit mode if you have the option (select Aperture and choose get info) and authorize (using whatever key you purchased).

12 Decide on a new hard disk area for you new Ap 3 library, with plenty of legroom.

13 Switch off faces if you want. Mileage seems to vary on this.

14 Import you projects one by one. Watch and observe for corruption, problems etc. on a project by project basis.

15 Think Zen - each project was lovingly made, and should be treated, individually, that way.

16 Rest easy that you have your Ap 2 library stored away. You can always go back to it if you follow this plan. (Although of course new projects in Ap3 will forever belong there).

Feb 15, 2010 1:34 AM in response to DiploStrat

When we last saw our Zen master ...

The images were moved and AP3 said that it wanted to "process" some 10,000 items and had 9,500 thumbnails queued to be rebuilt.

Processed up to 2,500 items and stalled for well over an hour. Minor disk I/O, CPU maxed. I wanted, at all costs, to avoid aborting anything, so I tried to "pause" the task. Took about an hour to pause and finally quit AP3. (Longest wait was for it to not "update sharing" info.)

This done, I shut down the Mac and then restarted.

The Mac came right back. I then started AP3. It showed 3 items to process and rebuilt the thumbnails in just a matter of minutes. At that point, I quit AP3 and restarted twice, doing the first two rebuild options for the database.

I compared the image count with the original AP2 library and they are the same. With around 10,000 images, I can't swear that there are no problems, but test edits, reprocessing, etc., all blaze right along. Performance is better than AP2, even with 100MB+ TIFF files.

All I can guess is that Apple underestimated the conversion effort required for big libraries and may have a couple of memory leaks or similar in the conversion code.

Other than that, AP3 is clearly a tremendous leap forward. Let us hope that they come up with some bug fixes in 3.1 very, very soon.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Zen and the Art of Migration to AP3

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.