MAC Lion and Aperture 3 - very slow

SnowgirlSnowgirl Registered Users Posts: 2,155 Major grins
edited August 7, 2011 in Finishing School
I just spent about 3x as long as I should have editing 21 images for a client. Aperture kept freezing and that bloody wheel just kept spinning. Aaaghhh!

Installed "Lion" this week. Could this be the problem?

Not a happy camper!
Creating visual and verbal images that resonate with you.
http://www.imagesbyceci.com
http://www.facebook.com/ImagesByCeci
Picadilly, NB, Canada

Comments

  • carmel6942carmel6942 Registered Users Posts: 154 Major grins
    edited July 31, 2011
    My experiance with lion has been very good Aperature runs better than it did in leopard. All the reading I did on lion before I installed said that Aperture ran better.

    You might verify and repair the disk permissions using disk utility



    Snowgirl wrote: »
    I just spent about 3x as long as I should have editing 21 images for a client. Aperture kept freezing and that bloody wheel just kept spinning. Aaaghhh!

    Installed "Lion" this week. Could this be the problem?

    Not a happy camper!
    Carl
  • DavidTODavidTO Registered Users, Retired Mod Posts: 19,160 Major grins
    edited July 31, 2011
    You're running the most recent Aperture update?

    EDIT: a quick google search shows that others are having this problem and that it looks like it may be a memory leak issue causing large swap files. If this is true an update should be coming shortly to fix the bug. (one would think!)
    Moderator Emeritus
    Dgrin FAQ | Me | Workshops
  • SnowgirlSnowgirl Registered Users Posts: 2,155 Major grins
    edited August 1, 2011
    DavidTO wrote: »
    You're running the most recent Aperture update?

    EDIT: a quick google search shows that others are having this problem and that it looks like it may be a memory leak issue causing large swap files. If this is true an update should be coming shortly to fix the bug. (one would think!)

    Thanks. Here's hoping. My software is all up to date according to my check. I will try checking the repair permissions thing though. Didn't think of that.
    Creating visual and verbal images that resonate with you.
    http://www.imagesbyceci.com
    http://www.facebook.com/ImagesByCeci
    Picadilly, NB, Canada
  • RichardRichard Administrators, Vanilla Admin Posts: 19,962 moderator
    edited August 1, 2011
    carmel6942 wrote: »
    You might verify and repair the disk permissions using disk utility
    That doesn't sound right to me. Incorrect permissions wouldn't slow it down--it just wouldn't work at all. Memory leaks related to the swap file sound like a more likely explanation.
    My Pics
  • SnowgirlSnowgirl Registered Users Posts: 2,155 Major grins
    edited August 1, 2011
    I did do a disk check and verify permissions, just in case. Still, it wants to freeze so I think it is the memory swap issue. Hope there's an update soon. Agghhh!:cry
    Creating visual and verbal images that resonate with you.
    http://www.imagesbyceci.com
    http://www.facebook.com/ImagesByCeci
    Picadilly, NB, Canada
  • kruegdudekruegdude Registered Users Posts: 1 Beginner grinner
    edited August 7, 2011
    A couple of things I've noticed about Aperture running on Lion in a 2011 iMac with 12G memory.

    After running for a while and being the curious sort I launched Activity Monitor, sorted on the "Real Memory" column (I think I had to enable that one manually) and right off the bat saw that Aperature and Safari were some of the heavy memory users with Aperature at about 2GB and the Safari/Safari Web Content pair running about 1.2G.

    I did a little experiment with Aperature and importing pictures. I stopped and started Aperature and it came consuming 340MB. I then imported a directory of about 185 jpegs each averaging about 700K in size (these are from an old 3M Pixel camera). It took maybe 15 seconds for Aperature to say it was finished and the memory had climbed to about 1.2G. I also noticed that for about 30-45 seconds after it said it was finished Activity Monitor was telling me that Aperature was consuming over 150% cpu so there was some background processing of the new pictures going on. I then selected Split View, selected the first picture in the film strip and used the right arrow key to progess from start to finish, selecting each picture. While I was doing this I checked on Aperatures real memory and it steadily grew until it seemed to max out at around 3.6GB. Once I stopped interacting with Apertures its real memory started to drop until it reached around 2.1GB.

    Of course the real memory would differ based on the total memory on the system but it seems to like to head towards that magic 4GB number (even though it a 64 bit app).

    Also, I think that maybe I should have been using the Virtual Memory column instead of Real Memory but since I had about 4GB of free memory showing it wouldn't matter. I suspect on smaller systems the Virtual Memory column would be a better guage of the memory usage.

    One other thing. I went back and scrolled through the film strip again and noticed that Aperatures memory did't really get much about 2.3GB so maybe there's some caching going on.

    I decided that after seeing these numbers that I would go ahead and max out my memory to 16G. I ordered it from a 3rd pary vendor as Apple's prices are too extreme for me, bumping it by 8G cost me around $65. Unfortunatly the iMac only has 4 slots so I'll have to swap out the 4G's for the 8G's but I think it's worth it.

    Hope this helps in some way,

    Bill
Sign In or Register to comment.