Skip navigation

Should I store my cr2 files in the aperture library?

242 Views 3 Replies Latest reply: Aug 7, 2011 9:29 AM by fredfromknoxville RSS
fredfromknoxville Calculating status...
Currently Being Moderated
Aug 4, 2011 6:10 PM

I have noticed aperture slowing, pausing and even crashing recently. I was wondering if storing too many cr2 files in the aperture library might cause this. At this time I have a little over 6000 cr2 files in the aperture library.

Aperture 3, Mac OS X (10.7)
  • Nigel Paterson1 Calculating status...

    I have probably 10,000 CR2 files in an Aperture library stored on a Drobo, connected by FW800 to an iMac 27. It can be slow to load the library and isn't as fast as working off the internal drive, but is stable and consistent. (I can't keep everything on theinternal drive, 1TB isn't big enough.)

     

    I would be looking at making sure you have enough hard disc space (20 per cent free is good) and a decent amount of RAM in your machine before worrying about the amount of images in Aperture.

  • Kirby Krieger Level 6 Level 6 (11,555 points)

    Generally, no.  And generally, size alone is not a problem.

     

    I regularly run Libraries with 30,000 24 MPxl Images, both from the system drive or from external drives, and have no problems.

     

    I built up a Library of 1 MB JPG Images to 300,000 Images in order to test Aperture and did not encounter any problems except with Faces.

     

    Although I haven't tested it directly, my sense is that Aperture performs better with large Libraries when the Images' Masters are Referenced and located on a separate drive from the Library.  Put the Library on your highest-performing drive (almost always the system drive); put your Referenced Masters on a fast drive.

     

    The first things to check if Aperture begins to behave poorly are (off the top of my head):

    - drive space (Aperture needs a lot of free space on your system drive

    - other programs (Aperture is hardware intensive; a poorly written utility can slow the OS a little -- but that little can hobble Aperture on that machine)

    - Library corruption (Force-quitting can do this -- run "Repair")

    - File fragmentation (OS X does a good job preventing this, but I still recommend defragmenting large Libraries once a month.  Copying to a second drive, and then copying the copy back, defragments files.)

    - Also, make sure your copy of Aperture is up-to-date.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.