Currently Being ModeratedJan 21, 2013 8:11 PM (in response to gjsmith)
Are you sure it's not sharing previews with iWork and iLife? That's what mine does at exist, because I have it set to do that.
Currently Being ModeratedJan 21, 2013 8:22 PM (in response to gjsmith)
I'm with William. Strongly suggest the following:
- Don't force-quit Aperture.
- Any time you force-quit, repair and/or rebuild your Library before using it again.
- Let it run. It may take 3 full days to do it's basement record-keeping, but once it's done you shouldn't have to wait nearly as long again. The legions of Bartlebys down there have a lot of work to do on your newly-created 3/4 TB Library.
- And do turn off sharing Previews if you don't want to share Previews. You can save some time (usually) by setting "Aperture Preferences➞Previews➞Share Previews with iLife and iWork" to "Always" instead of to "When quitting"
Currently Being ModeratedJan 22, 2013 7:24 AM (in response to gjsmith)
You are not alone! This "Lib update at close" mystery is wierd. I cant figure it out or know what Ive done to cause it. For my 80K images it takes another thirty minuets to finish updating before it closes Aperture. Once it did it after I successfully backup a vault and wanted to close down the computer. I need to take better notes when it happens. Oh and sharing Peviews is set to never.
Currently Being ModeratedJan 22, 2013 12:40 PM (in response to Kirby Krieger)
This is different (I think)--the Library begins updating (as second drop-down) after the updating-for-preview-sharing drop-down runs. I'm baffled as to what exactly Aperture is doing, and why it would take one second per item to do it. (2m items @ 1 sec per item is over 20 days of a frozen Library) I had preview sharing set to Always, but just changed it to Never; maybe that will help.
Currently Being ModeratedJan 22, 2013 1:13 PM (in response to gjsmith)
I'm baffled as to what exactly Aperture is doing, and why it would take one second per item to do it.
Have you the Actiity Viewer open? That should show you what Aperture is up to (WIndow > Show Activity). Or does it not show anything useful but "processing?
Currently Being ModeratedJan 22, 2013 1:26 PM (in response to gjsmith)
I still think your best path forward is:
- _Rebuild_ Library
- Close Aperture
- Let it run at least 24 hours.
Often the initial time estimates (by computer or observer ) are inaccurate due to extrapolating from a non-representative data set. iStatMenu (or similar, including the OS X Activity Monitor) may give some insight into what (if anything) Aperture is doing. Be sure to have a lot of free disk space (> 50 GB is my rule-of-thumb for huge Aperture Libraries) on your system drive.
Obviously, 20 days is too long to let it run. I have never had a Library run any task without finishing longer than 90 hours. (That was with a test Library that is: >6,000,000 files, >600,000 Images, > 1 TB.)
IME, the database handling and maintenence of Aperture is superb. The limitation in Library size seems to be the time it takes to do some administrative tasks.
Keep us posted.
You might also try turning off Faces. This was useful with earlier 3.x versions, but was, afaict, cured by 3.2. I suspect that Aperture does some work on the Faces database without reporting that in the Activity window.
Message was edited by: Kirby Krieger
Currently Being ModeratedJan 22, 2013 1:44 PM (in response to léonie)
The Activity Window closes. I get this updating behavior when I go to Aperture>Exit. The the drop down banner appears (the same drop down banner you get when you Merge or rebuild or repair a library).
Currently Being ModeratedJan 22, 2013 1:55 PM (in response to Kirby Krieger)
I will go for the repair later this week when I can clear out a 24 hour block of time. The affected Library is a relatively-svelte 520 GB (all managed), so hopefully Aperture can plow through it in that amount of time. I'll report the results.
I will look into iStatMenu; the open ports and files and sample process results in Activity Monitor are pretty much gibberish to me, although I was interested to note that Aperture hung 136 times a couple of days ago when I merged in a 722 GB managed Library.
I'm still running 10.6 so haven't upgraded past 3.2.4; sometimes I wonder if the OS.7-8 versions of Aperture perform better.
Thanks again for the help.
I concur with Faces: I tried it once and it is pretty much useless for my shooting.