Welcome to the MacNN Forums.

sknapp351 · Jan 10, 2007, 04:09 PM

I posted a while back on the CS3 Beta thread that CS3 ran horribly poorly on my machine, but I have come to realize that it was Aperture causing the problems. It used to run fine, but about the same time CS3 Beta came out I got a Nikon D80. Now whenever the application is running or just been quit my machine is horribly slow. Like 15 seconds for the dock to come out from hiding when I scroll over it kinda slow.
Whenever I try to quit Aperture it says that the application is currently processing previews and asks me not to quit. I tried leaving it running for a few hours while I was out, and when I got back Aperture was not using any processor. Then I quit the app and restarted it a few minutes later to the same behavior. I have tried reinstalling the app, cleared application casches with Onyx, and repaired permissions. Any other ideas?

Here is a pic of activity monitor when it is happening:

sknapp351 · Jan 10, 2007, 04:11 PM

By the way, this all started a couple weeks before I dropped my laptop.

SAm

http://forums.macnn.com/69/powerbook...o-vs-pavement/

mduell · Jan 10, 2007, 04:39 PM

How much memory do you have? Can you feel any disk activity while it's being slow?

sknapp351 · Jan 10, 2007, 05:05 PM

Sorry, Can't believe I forgot to post system specs. It is a 2.0 Ghz MBP with 2Gb ram, x1600 with 256mb VRAM. There are no system hacks or third party software running, I do have Onyx which I use only when things go wonky.

I can feel disk activity under the left palm rest next to the track pad.

Thanks
SAm

krove · Jan 10, 2007, 08:02 PM

How long have you been running Aperture? I know that when I migrated my iPhoto library of 6000 5 and 8 megapixel photos that it took a long time for Aperture to get all the previews generated on my MBP (same specs) and my computer performed like molasses. That only lasted the first day and some of the night. I'm not sure if you have to leave the application running for it to complete.

When not in use, Aperture takes 0% CPU, 19 threads, ~200 MB real memory, ~650 virtual memory.

sknapp351 · Jan 11, 2007, 05:53 AM

I had thought about that. I have been using Aperture for a few months with no problems. My iPhoto library has been in for some time. It seems that the issues started with the D80. I have let it run for a few hours hoping that it would get done with whatever it needs to do, but the behavior starts right back up every time I open the app. I reinstalled the RAW update that came out following the introduction of the D80, but no change.
Thanks
SAm

Goldfinger · Jan 11, 2007, 06:07 AM

In aperture go to the "Window" menu and at the bottom of that menu select "Show task list". It should tell you what aperture is doing. If it doesn't say anything something's weird is going on.

OreoCookie · Jan 11, 2007, 06:33 AM

Aperture uses all available resources for certain tasks. It took over night on my 2 GHz ProBook (2 GB RAM) to generate all previews of about 9k photos (mostly 4-5 MP jpgs). It'll last a lot longer if you use RAWs with a much higher MP count.

sknapp351 · Jan 11, 2007, 07:24 AM

Looking at the Tasklist shows that it is still processing previews. Thanks Goldfinger.
I guess the 10mp Raw files are a bit hefty for my computer and Aperture. Thats unfortunate cause I take a lot of shots and don't know if I can wait hours until Aperture is ready to let me use my computer.
SAm

OreoCookie · Jan 11, 2007, 07:48 AM

If you use Aperture, you don't need to wait. It gives foreground processes a higher priority and will wait with these background tasks until you don't use Aperture anymore. (However, Aperture will try to create previews for the pictures in the current project so you can browse through the pictures much quicker.)

So if you want to edit your pictures, there is no need to wait!

sknapp351 · Jan 11, 2007, 11:19 AM

Unfortunately when I have Aperture open my entire computer slows to a point of unusable. It runs slower than my Lombard G3 with 10.3. The dock takes 10 to 15 seconds to appear from hiding, it will take 5 seconds or more for a window to close. Command-Tab will take 5 seconds or more to react. If I am playing music on iTunes that is stored on my HD it will sometimes stutter. I mean it is really slow. Aperture is usable, but suffers from the same hesitations.
The weird thing is, I just had to pick up a friend from the airport, and before I left I watched the Task List in Aperture finish processing all the previews, and the system became responsive again. Now, when I returned I opened Aperture again and the system slowed down. I looked in the task list and it says it is processing previews, but only 4 this time ( last time there were over 20 ). Now where did it find new stuff to process?
Weird.
SAm

legacyb4 · Jan 11, 2007, 11:28 AM

I'm planning to get a MacBook soon and wondered if anyone can comment on performance seeing as it can thrash the performance of an MBP.

I was watching some of the tutorial videos and am really keen on the integration with iPhoto; the one thing that wasn't made clear is if you use Aperture to edit referenced files in iPhoto, the iPhoto image isn't actually altered which means those Aperture changes won't be visible?

sknapp351 · Jan 11, 2007, 11:52 AM

Please understand that for the first few months I had Aperture I had no problems what so ever. I first noticed problems when I got my D80. I never had problems with a 20D, D70, or a Sony FC-717. I don't see this as being a normal issue with Aperture. I don't know what it is, but up until a couple weeks ago I LOVED Aperture.
SAm

chapman · Feb 28, 2007, 01:15 PM

Aperture on my Macbook Pro seems fine until it invariably starts processing previews, then I begin to cry and pull my hair out. Apple should be hit with a class-action on this. No program should be allowed to suck-in and obfuscate your data so that it is nearly impossible to escape. (The latest version allows you to avoid this by leaving your images scattered all over the place.) No program should present you with a command button that, when clicked, does nothing for ten seconds then spins a beach ball for 30 seconds, only to leave you back where you started, because if you don't hold the button down the whole time you have to suffer through it again! When I have modicum of spare time, I plan to write a program that parses the Aperture XML, retrieves your images, and creates an easy escape route to Lightroom. Of course, you'll lose all your raw tweaks.

-Steve
3dlidar.com

CaptainHaddock · Mar 1, 2007, 04:17 AM

So far, I am extremely impressed with Aperture on my 2.33 MBP. While it was importing and generating previews from my large iPhoto library, I did happen to open Activity Monitor and see it taking 120% or so of CPU. However, I was also using several other apps at the time without a hiccup or beachball.

CatOne · Mar 1, 2007, 12:01 PM

Originally Posted by chapman

Aperture on my Macbook Pro seems fine until it invariably starts processing previews, then I begin to cry and pull my hair out. Apple should be hit with a class-action on this. No program should be allowed to suck-in and obfuscate your data so that it is nearly impossible to escape. (The latest version allows you to avoid this by leaving your images scattered all over the place.) No program should present you with a command button that, when clicked, does nothing for ten seconds then spins a beach ball for 30 seconds, only to leave you back where you started, because if you don't hold the button down the whole time you have to suffer through it again! When I have modicum of spare time, I plan to write a program that parses the Aperture XML, retrieves your images, and creates an easy escape route to Lightroom. Of course, you'll lose all your raw tweaks.

-Steve
3dlidar.com

Sheesh, put a sock in it. First, let Aperture generate the previews and it will speed up. Second, you can export your RAW files along with all your IPTC keywords. Just click "export masters" and specify a location. Click the checkbox and there are the XMP files, there is no need for you to parse your images.

As for this "scattered all over the place" BS, you have explicit control over exactly where all your images go. See the "relocate masters..." option.

Class action, nice.

nerd · Mar 1, 2007, 03:17 PM

I glad I'm not the only one that things Aperture is slow. I'm on a Dual 2 Ghz G5. What really helped the speed out for me was bumping my RAM up to 4.5 gigs (I also leave a bunch of apps open).

I think the biggest slowdown is loading the raw files off disk. When I was at the Apple store playing with a 3.0 Ghz Quad with 4 gig ram and Aperture still felt slow until the full picture was loaded. Just my observation, not science.

-Brad