Aperture running at a crawl since lion upgrade

Gerry

Everything you are saying is correct. Unfortunately, in these cases it is not a matter of simple performance tuning, but software crashes traceable to certain components of the OS. Having said that, the 4 GB minimum may need to be revised upwards, pending what Apple comes up with.

In my case, all underlying issues are masked when upgrading to 12 GB and running in 64 bit mode, which indicates that the lack of proper disk management and performance tuning is not the culprit. If it were, similar issues would manifest, regardless of RAM size and data path size.

sorinfromtoronto

If all I have said is correct, has the user tried simple performance tuning ? In my experience quite often simple performance tuning can be a good place to start before becoming too despondant that there is definitely an OS problem.

I'm not implying that there is not an OS problem, I have submitted feedback myself to Apple re an Aperture issue, unrelated to this problem, since upgrading to Lion.

I have also come through numerous OS upgrades since starting with Aperture 1.5...!!

But too often people innocently get misled in forums that there is nothing they can do to resolve their issue because they do not have enough RAM (for example) when all the time their hard drive is just crammed full of photographs and movies...That's why I suggested a simple resolution to start with....Then start by going up the ladder of fixes, not start at the top & work down..!

I agree that the 4GB RAM minimum ( I did mention that more would be preferable) will soon need to be revised.

FWIW I'm running a 2007imac on 4GB RAM in 64 bit mode with no issue's, because I maintain a good simple maintenance policy of not overcrowding my internal hard drive, and running Aperture using the 'Referenced master's" method.

I use two 2TB external hard drives to store all my masters (I only shoot RAW) and I have over a 1TB library split between two external hard drives...runs just fine! And I use Aperture & CS4 on a daily basis.

I also agree that 12GB would be the ideal, but what if the user who posted the question only has 4GB, and they are maxed out at 4...! Are they to believe that that's it..! their 2009 mac is no longer viable..!

I disagree that disk management & performance tuning can be ruled out...which is what you are saying, because you have 12GBRAM...and no issues..

But I have always believed that this forum is about helping other's to work with with what they already have and to help them get through current issues before spending their money on something they may not need.

Sorry if I wasn't clear. All of the basic maintenance and tuning tasks you mentioned had been done.

What version of OS are you running on the 2007 iMac you mention in your post? Do you happen to have an SSD in it?

Thanks

Hope you guys don't mind if I jump in here.... I have a mid year 2007, maxed at 4gb of ram. I have a 750bg internal hard drive with 320gb's stored on it. (I have a 70gb iphoto library & a 40gb aperture library on this internal).

I also have a Drobo RAID external drive with 4x 2tb drives in it for a total of 8gb (less the overhead redundency files). I keep 1tb of itunes movies and music on this drive and about 2.5tb's of my FCP and iMovie projects, video, and misc media on the Drobo. I also have two additional backup hard drives, both seagate 1.5tb. One for Time machine, and one for Superduper, which is a bootable mirror of my internal.

My system is squeaky clean.... you can smell the bleach coming out of the fan..... Clean and running smooth and happy.

That said, when I upgraded to Lion, Aperature 3 slowed to a crawl. I ran a few memory applications to see where my memory was going. iMovie uses about 1/2 of my ram (2gb) when running. The ram is freed up as soon as I close iMove. Aperture, running in 64bit mode, ***** all the available ram from my system. Leaving me with between 30-70mb's.... and sometimes bottoming out to 8mb's of ram! Obvously, my sister cant run (and certainly Lion cant run) on this tiny amount of residual ram.

I switched Aperture to 32bit mode and it's better. Not great, but better. Aperture ran better in Snow Leopard. But running Aperture in Lion while in 32bit mode is not too bad.

I really don't think Apple is looking back to fix these issues. They built FCP-X, Aperture, etc, to run on the newer graphics chips, 64bit systems with oodles of ram.... etc....

And they've got me saving for a newer system, so the koolaid they sell works....

sorinfromtoronto...

Unfortunately I don't have an SSD, I have 500GB SATA disk internal hard drive Intel Core 2 Duo processor and as mentioned 4GB RAM. And thats it maxed out..!

Like asheri I run my mac very lean and fortunately it runs just fine.

I always believe that when you buy a mac, any mac, that once they get to about 4years old, with new innovations coming along the moment you walk out of the store with your new unit, you need to start either running it very clean or think about buying a newer model.

It's a compromise, technology moves on, Apple are leaders and if they remain static for too long competitors will overhaul them.

Each time Apple release an update to an OS there is pain... even just an update to an app like Aperture is painful..but there are workarounds.... Not an ideal situation I hear the cry, but inevitably we all have to work around an issue in the end.. no matter how much we scream..!

I dont think it will be too long before I renew my system, due to current advances with processors, SSD availability (and cheaper too) But I'm pretty sure I can squeeze another year at least out of it... just, then I'm going to have to renew....

So no matter how much we yell.... Apple moves on... FWIW they dont come here to these discusions either so it's no use yelling at them here... they dont hear...!

The best way to get Apple's attention is to submit feedback with issue's... they listen then to large numbers...

asheri..

As I dont shoot movie's, I am strictly photogrgaphic I have removed imovie, I dont keep my music on my mac, I really only use my imac for photo management and editing purposes.

I have also turned of faces & places in Aperture, I dont need them. My client's are only interested in looking at photograph's...

With this new Lion update when I hit F on my keyboard to go to full screen view... Aperture now fades out my desktop image to the left of screen.. and finally (slowly) gives me my full screen image..!! ***....!!! I really dont need my client's wtaching this gimmicky effect...Aperture is a pro app.. ! When I hit F I want to go straight to my full screen image (as before Lion)..Not watch the Andromeda galaxy exiting left...!! 🙂

So I have submitted feedback pleading for the ability to turn off this feature in preferences... really thats my only issue so far with Lion.. Other than that it's running fine...

Kind regards to you both... Gerry

Well said Gerry.

-Allen

Hey Allen... Thanks... I was grateful for your help a few years ago also...more than once..!! Regards.. Gerry

Thank you Asheri,

Switching to 32 bit mode fixed my performance problems. Mid year 2008 iMac, 4 gig of RAM.

In 64 bit Aperture crawled. In 32 bit, it's back to SL performance or faster!

Thanks again!

Can someone please explain the steps needed to exclude the Aperture library from Spotlight and Time Machine? (I think I've done that for Time Machine, but I know I haven't for Spotlight.) I've done all the other things recommended in this excellent thread. Thank you!

Mark,

System Preferences > Spotlight > Privacy > +

Sorry for the late reply, too much travelling! Anyway - I am using 64bit mode so I should be suffering! Sample process memory sizes memory as follows:

Real 1.43Gb

Virtual 4.83Gb

Shared 0Gb

Private 1.34Gb

Virtual Private 1.96Gb

This after opening a library with 64 RAW images and processing 4 of them (crop, retouch, saturation, definition). Machine has been running for 3 days with Aperture running continuously over that period.

It just works fine for me and did so even before the 10.7.1 update. It's not at all obvious why I'm lucky with it and other are not. I've spend 2 weeks travelling around using the MacBook Air to process some 3000 RAW files in total over 4 libraries all based on a USB external drive. I've had Aperture fall over a couple of times, but I think that is when the external drive connection was interrupted so it's forgivable. Over thqat time I've not lost any data and processing speed is what I'd expect from a machine of this spec; not blistering, but adequate.

Tim

MacBook Air 11-inch, Late 2010

Processor 1.6 GHz Intel Core 2 Duo

Memory 4 GB 1067 MHz DDR3

Graphics NVIDIA GeForce 320M 256 MB

Software Mac OS X Lion 10.7.1 (11B26)

Aperture version 3.1.3 build 1952400.4

Tim, thank you for taking the time to respond. You are correct: the bug does affect only part of hardware configurations. I did provide Apple with a pile of data, so all we can do now is wait.

Cheers

Sorin

Tim - when you installed Lion, did you do a clean install or an upgrade?

I'm curious if wiping my hard drive would be worthwhile. The crashes in 32 bit mode are getting to me.

Stephen

Good question. It would also be interesting to see what your system configuration is, com pad to Tim's.

typo: I meant "compared"