Hakeswill

Q: More issues with poor Aperture performance

Sorry to start another thread on poor Aperture performance, but none of the other threads I've found have been of any help (alas). I'm running Aperture 3.4.5 and am experiencing stupefyingly poor performance. It's not an issue of slow operation, but of regular beach balls. When I start it up, it beach balls. Then it stops and I foolishly try and do something, like move the mouse, and it beach balls again. This goes on for about a minute.

 

If I start editing, say, and then do something else, like switch to my library, it beach balls twice. Always a double beach ball. The editing process isn't slow as such, like it would be if my Mac wasn't powerful enough, it's just that I get regular issues of Ap freezing on me. After a while the app does start to run slowly, which makes me think that there's a problem somewhere.

 

I'm running a 15" Retina MBP with a 2.6 GHz i7, 16 GB of RAM and a 256 GB SSD, which is currently just over half full. My Ap library (managed) is about 37 GB, but it used to be bigger until I archived most of it.

 

Any ideas? Thanks!

Posted on Sep 20, 2013 6:31 PM

Close

Q: More issues with poor Aperture performance

  • All replies
  • Helpful answers

Previous Page 2
  • by Hakeswill,

    Hakeswill Hakeswill Sep 21, 2013 4:58 AM in response to Ernie Stamper
    Level 1 (4 points)
    Mac OS X
    Sep 21, 2013 4:58 AM in response to Ernie Stamper

    Ernie Stamper wrote:

     

    Have you tested with this wireless external drive not connected?

    Yes, makes no difference.

     

     

    In the other User Account, hold down the Option Key while clicking to launch Aperture.  What libraries are offered in the resulting dialogue?  Is the primary library that you use in your normal user account listed?  If so, can you choose and open it?  (there might be a legit issue of permissions with that, but check)

    It isn't listed, but I can navigate to it. I can't open it, so I navigated to it in the finder and allowed myself read and write permissions (in fact I allowed the whole file path). But oddly that doesn't work. It says that the permissions are wrong. When I go back to my main user account to check on the permissions, it recognises that my new account has read/write access. Not sure why it's not letting Ap open it in the new account.

Previous Page 2