HT4007 aperture running slow

I am running aperture and it runs very slow and freezes up any suggestions?

No one reading can possibly form an intelligent response from the information you've provided.
Post
- what the problem is
- how you have confirmed that it is a problem
- what you have done to rectify the problem
- what the results of your attempt to rectify the problem were
and
- what version of Aperture
- what version of OS X
- your hardware configuration, inc. system drive free space
- whether you changed anything recently
- whether you are have problems with any other applications.

Similar Messages

  • HT4007 Aperture is Slow - What do I do?

    Almost everything I do in Aperture is slow and it's gotten worse over time.  This doesn't happen with other applications it's specific to Aperture.
    Clicking the import tab takes several seconds.
    Clicking to a project causes a beach ball
    My library is huge. 35,000 pictures
    The Vault requires 178GB.
    I'm running Aperature 3.5.1 on an imac 2011 with 8GB of RAM. Everything is updated.
    What should I do to improve performance?
    Will breaking down the library in to parts help? How do I do that?
    Thank you for your help!
    Bob D. in Huntington Beach.

    My library is huge. 35,000 pictures
    The Vault requires 178GB.
    Is your library on an external or the internal drive? How full is the internal drive? Do you have at least 20GB free on your System drive?
    Do you use plug-ins? If yes, have you checked, if they are compatible?
    When did the slowness start? After updating software or installing new software? After importing new images?
    Will breaking down the library in to parts help? How do I do that?
    The library size alone cannot cause the slowness, so spliting it will probably not help.
    Try to narrow down the problem;
    You may have imported media, that cannot be processed;
    Your library may need fixing,
    your user account may have wrong settings,
    or you may have a system wide problem.
    To check for corrupted media in your Aperture library, launch Aperture, while holding down the Shift key. Is Aperture still slow?
    To check if the library is causing the problem create a small test library - just use the command "File > Switch to Library > Other/new" and create a new library; import a few images and test.  Do you see the same slowness?
    If even a new library does not help, repeat the experiment, but while working in a different user account. Is Aperture more responsive, if you are using a different account?
    Then post back, with the results of your experiment.
    Léonie

  • Aperture running slow on my macbook Pro

    Hi,
    I have a 2.0 GHZ macbook Pro with 2G of ram and a 7200RPM hard drive. Processing runs smoothly when I first start Aperture, but gradually, the computer starts to slow down (the CPU gauge jumps), and the computer actually pauses for several seconds. It gets to the points that the changes are no longer in real-time, that is, when I adjust the saturation (or make curve adjustments), I have wait several seconds before the changes make it to screen. There are no other programs running while Aperture is running, and the files are RAW files from my Nikon D200.

    This is my experience as well. Aperture is somewhat snappy at first then, over time, slows down and becomes very sluggish.
    I'm currently using "only" 1 GB of ram and am considering adding a second gig. But your experience seems to indicate that 2 GB of ram does not resolve the situation.
    What file sizes are you working with?
    I'm primarily working with file sizes of 60 to 70 MB.
    Wondering if Aperture, in general, has trouble handling larger file sizes.
    MacBook Pro   Mac OS X (10.4.7)   Aperture Version 1.1.2

  • Aperture running slow with lion

    Ever since I installed Lion, Aperture is going at a snail's pace..Is there an Aperture upgrade that will fix this?

    The solution was to press and hold the option and command keys while starting Aperture, and then selecting Repair Permissions. This seems to have fixed the problem. Thanks.

  • I have iMac and need a good photo editing program to use.  Reviews say aperture runs really slow with Lion, any suggestions?

    I need a program where I can remove objects and touch up dead grass, etc.

    Reviews say Aperture runs really slow with Lion, any suggestions?
    To add on to Corky02 answer:
    The recent Aperture release AP 3.3.x is very efficient, both on Lion and Mountain Lion. But you need a decent hardware to support it. The older Macs will have problems with the storage and CPU requirements. For good performance on large raw images plenty of RAM is important, at least 4GB, but 8GB would be much better, and your library should be on a fast disk, preferably on an internal drive. And don't let the system drive get too full.
    Many reports about Aperture being slow are due to putting the Aperture library onto slow disks or acessing  the original image files over the network, insufficient RAM, or corrupted or  ill-designedAperture databases.
    Aperture excels at all kinds of image processing that can be considered image developement - raw processing and color/lighting adjustments, but does not do compositing. If you are shooting raw and want professional image developement I'd recommend to do this in Aperture and not in iPhoto - you will have much more control over this in Aperture (after a steep learning curve). You can also  repair and retouch the image to correct minor blamishes. For graphics compositing and inpainting you can set up an external editor and send your images from Aperture to this external editor - any of the editors Corky recommended would be o.k. for this.
    To see, if you will want the advanced image processing in Aperture or the easy to use, more basic options in iPhoro will be sufficient to you have a look at the Aperture User manual, or the tutorial on the support page: Aperture Support
    But Aperture is a professional apllication, not "plug and play". You should only consider it, if you are willing to spend some time on learning to use it properly and are willing to work your way through the manual.
    Regards
    Léonie

  • Aperture 3 runs slow, should I split my library into more projects?

    Aperture 3.4.5 is running very slow on my 2x 2.4 GHz Quad Core Intel Xeon 5.1 Mac Pro. My Aperture library is 609 GB and I have it on a internal HD with 2.94 TB of room available. I have been using Aperture since it first came out but I have only made 7 Projects in all that time. I just add additional folders and albums inside of those 7 Projects. I'm looking for a way to speed up Aperture because it has slowed down to a crawl, for example, when selecting more than a few images everything stops and I get a spinning beach ball for up to a minute. This is new behavior for Aperture. I have tried all of the recommended fixes such as repair permissions, repair database and finally, I tried rebuild database. None of these has helped.
    Somewhere I read that you needed to repair the database before you installed Aperture 3.0. I did not do this. That is the only thing I can think of that could be a cause of this, my hardware is more than adequate to use Aperture. I need suggestions...

    Somewhere I read that you needed to repair the database before you installed Aperture 3.0.
    If you repaired and rebuild your Aperture library since then, it should not matter.
    . I have been using Aperture since it first came out but I have only made 7 Projects in all that time. I just add additional folders and albums inside of those 7 Projects.
    I am concerned about that. Why only a few projects? Your projects must have more than several thousand images each. I found, that Aperture is slower, if the projects are very large and if I have many smart albums. Aperture becomes more responsive, if I split the projects and group the split projects inside a folder.
    I'm looking for a way to speed up Aperture because it has slowed down to a crawl, for example, when selecting more than a few images everything stops and I get a spinning beach ball for up to a minute
    How full is your system drive? You only mention the space available on your second drive, not on your system drive.
    When did this slowness start? After you imported new images or installed other software?
    Regards
    Léonie

  • Running Aperture and Slow Performance on MacBook Pro

    I am running a MacBook pro w 4 GM interal memory, lost of HD space, and OS 10.8.4.  Often when working with Aperture system performance seems very sluggish to the point of becoming unuseable.  Export of 20 images to mail can take 10 min.  It just becomes so slow as if strangled for memory.  I find I shut down other apps but don't think this should be necessary with current OS technology.  Any suggestions?  Thanks

    Have you checked what it going on, when Aperture becomes sluggish?
    I'd recommend to launch some diagnostic tools, if you have not already done so:
    Aperture's own "Activity Viewer": From the main menu bar: Window > Show Activity
    This will tell you, how Aperture is spending its time : rendering, previews, scanning for faces or places, raw processing. Inparticulur, check, if Aperture is hanging while processing one particular image or video over and over again.
    The Console window: Launch it from the Utilities folder in the Applications folder. Look, if you see error messages or warnings in this window, when Aperture starts to hang.
    The Activity Monitor: Launch it from the Utilities folder in the Applications folder. This window will tell you, which processes are using the cpu, the RAM, and doing page outs to the disk. You can see, if other processing are competing with Aperture and slowing it down, orif Aperture is starved for memory.
    How large are images? Do you have very large raw files or scans, or are your photos moderately sized?
    Is your library on the internal drive or an external drive?
    Do you see this slowness only with your main Aperture library, or also, if you create a new, small library with a few test images?
    Regards
    Léonie

  • Why does aperture run so slow

    i have loaded a very larg number of photos into aperture.  now the app runs so slow it is impossible to use.  what am i doing wrong?

    what am i doing wrong?
    Probably nothing.
    You might turn on the "Activity" window in Aperture, to see what Aperture is doing (from Aperture's main menu bar: "Window > Show Activity". After importing it will need plenty of time to render previews, detect faces, assign places, etc. Best let it run over night.
    Other things that might be a problem:
    Aperture will slow down, if the project are too large. Did you import all images into one single project? Keep the projects small, not much larger than about 200 images per project.
    And if your harddisk becomes full, you may slow down the mac considerably.Try to keep at least 20 GB of your harddisk free.
    You may have imported a corrupted image or an incompatible video. If that is the case, than Aperture will try over and over again to render a preview and not succeed. It might help, to disable the rendering of previews, until you have spotted the video or image that is causing the problem
    How much RAM do you have, and how full is your disk?
    Regards
    Léonie

  • Why does my computer run slower with Aperture installed

    I installed Aperture on my MacBook Pro and now it runs slow when the program is open. 

    Nikon,
    Aperture does lots of background processing after you first install it.  It is likely that Aperture is performing some of this processing as soon as you open it now.  You can get a good feeling for what it is doing if you show the Activity with {Command}-{Shift}-0.
    You may have to let Aperture crunch away for hours or even overnight before it is done.

  • MBP 15 inch i7 running APERTURE runs EXTREMEMLY SLOW right out of the box!!

    here's the gist of the situation.
    brand new 15inch i7 with 4 gigs of ram and high-res display and aperture pre-installed. The laptop is blazing fast UNTIL I open aperture.
    I only had safari with google and aperture open. Even with absolutely no pictures open, or projects, or RAW file conversions it brings this hercules of a laptop down to the speeds of an old windows 95 machine.
    I thought the problem was possibly the the new graphics switching, so i turned it off. It makes little to no difference.
    I seriously can't click on FILE without waiting 15 seconds before ANYTHING happens, and then I get a spinning rainbow curser for about 2 minutes! Then it finally opens the file menu...
    This is very upsetting considering I need use this software heavily in my work.
    Any suggestions????
    Much thanks for any suggestions.

    Thanks a lot! what you said is partially true. right after posting this i realized that the removable hard drive I have plugged in is formatted for, and has been used on a windows xp machine up until now.
    beyond aperture running slowly, the entire computer was running slow if I clicked on anything more than once, if it didn't open the first time.
    The moment I unplugged the hard drive (which was synced to aperture) the computer began to run like the mac OS that I love.
    Thank you for your time!

  • Can i make Aperture run faster ?

    To help those struggling to understand why their computer is running Aperture slowly, let me add a few thoughts to help out. I've been using the application since 1.0, bought a G5 quad to run it (launched on same day) with the stock video card. My Photographic interest was Landscape and macro work in film (hobby) and been using digital since 94 and now turned Pro adding Portrats and Weddings to my interest.
    How do i run Aperture at a decent speed ?
    1. Invest in good hardware. In any of Apple's product line max-out the graphics card option (except perhaps expensive Quadro fx4500), max out CPU option then the RAM. Invest as much as possible in the non-upgradeable components. Over time you can add more ram, but don't underestimate the importance of RAM in OSX. Keep your boot/application and data drives below 70% capacity as above this they start to slow down.
    2. Use the vaults and backup the library (don't forget any referenced images).
    3. When editing images, don't whang the sliders freely left to right. Be a crafstman, use the number adjustment arrows, with the modifier keys for fine tunng SHIFT and ALT. This is faster.
    4. If an image has a lot of spot'n'patches, do this first before any other adjustments (or untick their box in the HUD). Similarly for strighten, do this before H&S or exposure mods.
    5. Switch off previews, for marginal improvements.
    6. Don't use full-screen mode, its lovely, but with my awful graphic card it kills it when adjusting. Remove the projects window W and control bar D. Toggle the adjustments with I. Real estate is arranged better with the browser on LHS.
    7. Try culling the rejects with the viewer off V and maximise the thumbnail size. Suprisingly fast and effective when only going for rejects.
    8. After culling use the auto stack feature to reduce the number of images your viewing into 'like' shots. Helps when choosing your story for output.
    9. Setup some presets for varying degrees of edge sharpen and White balance as this helps get you get in the vacinity of where you want the adjustment. eg. I have five increasing degrees of edge sharpening intensity and six white balance settings (daylight, cloudy, shade, flash, tungsten, flourescent) which gets me closer to a good WB faster than playing with multiple sliders.
    10. Learn the keyboard shortcut.
    11. Use Aperture feedback. If your unsatisfied with anything then tell apple as well as the forums. So far we have seen big improvements in Aperture, some were really alpha/beta issues but it is clear Apple is serious about investing in this young Application. I hope they invest in the pixel-pushing, local editing, masks and layers abilities, but do it true to an intuitave workflow platform that Aperture has become.
    12. RTFM as well as buy a book - invest in your skills, become better, faster and ultimately more productive.
    13. Don't believe in bad luck !
    The reason for Aperture running sluggish when using specific adjustments is because i need to upgrade my video card. Fortunately, i can, but might invest in a MP for more storage.

    If You go to the Aperture site page for basic requirements needed to run it, It will state a Powerbook in fairly basic design will run the Application.
    And before I purchased Aperture, and as you can see I updated my RAM to 2 GB.
    I ordered this laptop with the top line of all hardware possible.
    So I could run also run a 20" screen.
    And no, I didn't pack the 20" in my suitcase.
    It's amazing how far you have to make sure people don't take one word and run with it.
    Not ONLY Aperture, but DDP (Digital Photo Professional), as I hate when people only use abbreviations for everything, and the person trying to learn something is slammed out the door for even looking.
    But both applications run pig azz slow. So much so, and I also use the Activity Monitor to keep watch over things in realtime.
    When things run this slow to the point you can't see a live change in the view,
    You don't learn much, and you can't complete a simple project.
    Like one person suggested earlier, just tweak the image one mark at a time.
    Well hey, we don't have 6 hours to make one adjustment.
    The processor is running at 100% and never backs off till you kill the application.
    Making the move from Canon G5, to a Canon 30D and a few thou in lenses, is about the biggest joke while in Europe. Yea, drag all this stuff you don't see to Europe, with 2 portable hard drives to keep the Mac hard drive happy.
    It all adds up to roughly a $7000 dollar mistake.
    The ads are a total farce. Get this, and do stuff beyond the norm.
    Yea Right, like your going to bring a G5 tower in a suitcase.
    Oh sure, I'll struggle with the software till get through with 20 images, and
    what if you have 300?
    Now, one question... Who's next , as far as an application that runs RAW images with no lag. With out all the BS.
    Power Book G4-1.67-2GB, Bluetooth Mouse & Keys   Mac OS X (10.4.8)   20" screen for dual view.

  • Aperture feels slower. Is there a maximum recommended library size

    What would you recommend as a maximum size for an Aperture 3 library? Is there a way to keep it running faster or safer?
    I have basically 2 big groups of photos (divided in folders with projects and albums inside), GUIDING-FISHING and FAMILY, it sounds ovious to divide it in 2 libraries, but I have mixed albums to upload photos to my iPad....
    How should I proceed If I decide to move all the photos related to GUIDING-FISHING to a new Library?
    Thank you! Regards, Pablo

    Hi Terrence and Kirby, Thanks for your quick response.
    My MAC is a MacBookPro 15" (model 8,2) with a 2.4GHZ Core i7, 8GB RAM and  a 750gb HD.
    I have about 95 gb free in my HD.
    It shown in the mac information that 133gb belongs to photos and the Aperture library weights 66,56 gb
    So Kirby says it can take 1 or even 2TB, that's not the problem....
    Do you think I need to adjust any preferences to make it run faster?
    I will reed the info and directions about basic mantenience on the library and get back to you.
    Have you ever used that macKeeper app that you get adds all over the internet? never even downloaded it, but you get adds all the time... is your mac running slow??...
    Thank you!

  • Mbp w/ mavericks running slow

    hi-
    everythign has been running slow since installed mavericks... wondering if i should do a clean install?? i've already repaired and fixed disk and permissions. delted software don't use. backed-up. archived to external drive some files. any ideas??
    here's the etrecheck report.
    Hardware Information:
              MacBook Pro (15-inch, Early 2011)
              MacBook Pro - model: MacBookPro8,2
              1 2.2 GHz Intel Core i7 CPU: 4 cores
              4 GB RAM
    Video Information:
              Intel HD Graphics 3000 - VRAM: 384 MB
              AMD Radeon HD 6750M - VRAM: 1024 MB
    Audio Plug-ins:
              BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
              AirPlay: Version: 1.9 - SDK 10.9
              AppleAVBAudio: Version: 2.0.0 - SDK 10.9
              iSightAudio: Version: 7.7.3 - SDK 10.9
    System Software:
              OS X 10.9 (13A603) - Uptime: 0 days 0:48:27
    Disk Information:
              TOSHIBA MK7559GSXF disk0 : (750.16 GB)
                        EFI (disk0s1) <not mounted>: 209.7 MB
                        tsume (disk0s2) /: 749.3 GB (672.18 GB free)
                        Recovery HD (disk0s3) <not mounted>: 650 MB
              MATSHITADVD-R   UJ-898 
    USB Information:
              Apple Inc. FaceTime HD Camera (Built-in)
              Apple Inc. Apple Internal Keyboard / Trackpad
              Apple Inc. BRCM2070 Hub
                        Apple Inc. Bluetooth USB Host Controller
              Apple Computer, Inc. IR Receiver
    FireWire Information:
    Thunderbolt Information:
              Apple Inc. thunderbolt_bus
    Kernel Extensions:
    Problem System Launch Daemons:
    Problem System Launch Agents:
    Launch Daemons:
              [loaded] com.adobe.fpsaud.plist
              [loaded] com.adobe.SwitchBoard.plist
              [loaded] com.google.keystone.daemon.plist
              [loaded] com.microsoft.office.licensing.helper.plist
              [loaded] com.oracle.java.Helper-Tool.plist
              [loaded] net.sourceforge.MonolingualHelper.plist
    Launch Agents:
              [not loaded] com.adobe.AAM.Updater-1.0.plist
              [loaded] com.google.keystone.agent.plist
              [loaded] com.oracle.java.Java-Updater.plist
              [loaded] com.wacom.wacomtablet.plist
    User Launch Agents:
              [loaded] com.adobe.AAM.Updater-1.0.plist
              [loaded] com.adobe.ARM.[...].plist
    User Login Items:
              None
    3rd Party Preference Panes:
              Flash Player
              Java
              WacomTablet
    Internet Plug-ins::
              o1dbrowserplugin: Version: 4.9.1.16010
              WacomNetscape: Version: 1.1.1-1
              Default Browser: Version: 537 - SDK 10.9
              AdobeExManDetect: Version: AdobeExManDetect 1.1.0.0 - SDK 10.7
              WacomTabletPlugin: Version: WacomTabletPlugin 2.0.0.4
              FlashPlayer-10.6: Version: 11.9.900.170 - SDK 10.6
              Flash Player: Version: 11.9.900.170 - SDK 10.6
              QuickTime Plugin: Version: 7.7.3
              googletalkbrowserplugin: Version: 4.9.1.16010
              SharePointBrowserPlugin: Version: 14.0.0
              AdobePDFViewer: Version: 10.1.1
              npgtpo3dautoplugin: Version: 0.1.44.29 - SDK 10.5
              JavaAppletPlugin: Version: Java 7 Update 45
    Bad Fonts:
              None
    Old applications:
              AU Lab:          Version: 2.2.1 - SDK 10.0
                        /Developer/Applications/Audio/AU Lab.app
              Accessibility Inspector:          Version: 3.0 - SDK 10.0
                        /Developer/Applications/Utilities/Accessibility Tools/Accessibility Inspector.app
              Accessibility Verifier:          Version: 1.3 - SDK 10.0
                        /Developer/Applications/Utilities/Accessibility Tools/Accessibility Verifier.app
              Clipboard Viewer:          Version: 3.0 - SDK 10.0
                        /Developer/Applications/Utilities/Clipboard Viewer.app
              Core Image Fun House:          Version: 2.1.46 - SDK 10.0
                        /Developer/Applications/Graphics Tools/Core Image Fun House.app
              CrashReporterPrefs:          Version: 10.7 - SDK 10.0
                        /Developer/Applications/Utilities/CrashReporterPrefs.app
              FileMerge:          Version: 2.5 - SDK 10.0
                        /Developer/Applications/Utilities/FileMerge.app
              HALLab:          Version: 1.6 - SDK 10.0
                        /Developer/Applications/Audio/HALLab.app
              Help Indexer:          Version: 4.1 - SDK 10.0
                        /Developer/Applications/Utilities/Help Indexer.app
              IORegistryExplorer:          Version: 2.1 - SDK 10.0
                        /Developer/Applications/Utilities/IORegistryExplorer.app
              Icon Composer:          Version: 2.2 - SDK 10.0
                        /Developer/Applications/Utilities/Icon Composer.app
              Instruments:          Version: 4.2 - SDK 10.0
                        /Developer/Applications/Instruments.app
              OpenGL Driver Monitor:          Version: 1.6 - SDK 10.0
                        /Developer/Applications/Graphics Tools/OpenGL Driver Monitor.app
              OpenGL ES Performance Detective:          Version: 1.1 - SDK 10.0
                        /Developer/Applications/Graphics Tools/OpenGL ES Performance Detective.app
              OpenGL Profiler:          Version: 4.5 - SDK 10.0
                        /Developer/Applications/Graphics Tools/OpenGL Profiler.app
              OpenGL Shader Builder:          Version: 2.1 - SDK 10.0
                        /Developer/Applications/Graphics Tools/OpenGL Shader Builder.app
              PackageMaker:          Version: 3.0.5 - SDK 10.0
                        /Developer/Applications/Utilities/PackageMaker.app
              Pixie:          Version: 2.5 - SDK 10.0
                        /Developer/Applications/Graphics Tools/Pixie.app
              Quartz Composer:          Version: 4.5 - SDK 10.0
                        /Developer/Applications/Quartz Composer.app
              Quartz Composer Visualizer:          Version: 1.3 - SDK 10.0
                        /Developer/Applications/Graphics Tools/Quartz Composer Visualizer.app
              Quartz Debug:          Version: 4.2 - SDK 10.0
                        /Developer/Applications/Performance Tools/Quartz Debug.app
              SA Color Finesse 3 UI:          Version: 3.0.6(275) - SDK 10.5
                        /Applications/Adobe After Effects CS6/Plug-ins/Effects/Synthetic Aperture/(CF3 Support)/SA Color Finesse 3 UI.app
              SRLanguageModeler:          Version: 1.9 - SDK 10.0
                        /Developer/Applications/Utilities/Speech/SRLanguageModeler.app
              SleepX:          Version: 3.1.1 - SDK 10.0
                        /Developer/Applications/Utilities/SleepX.app
              Spin Control:          Version: 0.9.1 - SDK 10.0
                        /Developer/Applications/Performance Tools/Spin Control.app
              Syncrospector:          Version: 6.0 - SDK 10.0
                        /Developer/Applications/Utilities/Syncrospector.app
              USB Prober:          Version: 4.4.0 - SDK 10.0
                        /Developer/Applications/Utilities/USB Prober.app
              Wondershare Helper Compact:          Version: 2.2.5.6 - SDK 10.5
                        /Users/mayte_eme/Library/Application Support/Helper/Wondershare Helper Compact.app
              Xcode:          Version: 4.2.1 - SDK 10.0
                        /Developer/Applications/Xcode.app
              Xcode SSH Authentication Agent:          Version: 4.2.1 - SDK 10.0
                        /Developer/Library/PrivateFrameworks/IDEFoundation.framework/Versions/A/Re sources/Xcode SSH Authentication Agent.app
              dynamiclinkmanager:          Version: 6.0.0 - SDK 10.5
                        /Library/Application Support/Adobe/Common/dynamiclink/CS6/dynamiclinkmanager.app
              dynamiclinkmediaserver:          Version: 6.0.1 - SDK 10.5
                        /Library/Application Support/Adobe/Common/dynamiclinkmediaserver/1.0/dynamiclinkmediaserver.app
    Time Machine:
              Skip System Files: NO
              Mobile backups: OFF
              Auto backup: NO
              Volumes being backed up:
                        tsume: Disk size: 697.84 GB Disk used: 71.82 GB
              Destinations:
                        kikuchi [Local] (Last used)
                        Total size: 465.14 GB
                        Total number of backups: 2
                        Oldest backup: 2012-04-15 21:58:00 +0000
                        Last backup: 2013-12-12 03:57:50 +0000
                        Size of backup disk: Adequate
                                  Backup size 465.14 GB > (Disk used 71.82 GB X 3)
              Time Machine details may not be accurate.
              All volumes being backed up may not be listed.
    Top Processes by CPU:
                   4%          WindowServer
                   2%          EtreCheck
                   1%          Google Chrome
                   0%          TextEdit
                   0%          mds
    Top Processes by Memory:
              160 MB          com.apple.IconServicesAgent
              156 MB          Google Chrome
              98 MB          Finder
              78 MB          mds_stores
              74 MB          WindowServer
    Virtual Memory Statistics:
              255 MB          Free RAM
              1.60 GB          Active RAM
              1.13 GB          Inactive RAM
              1.01 GB          Wired RAM
              630 MB          Page-ins
              0 B          Page-outs

    First, back up all data immediately unless you already have a current backup. If you can't back up, stop here. Do not take any of the steps below.
    Step 1
    This diagnostic procedure will query the log for messages that may indicate a system issue. It changes nothing, and therefore will not, in itself, solve your problem.
    If you have more than one user account, these instructions must be carried out as an administrator.
    Triple-click anywhere in the line below on this page to select it:
    syslog -k Sender kernel -k Message CReq 'GPU |hfs: Ru|I/O e|find tok|n Cause: -|NVDA\(|pagin|timed? ?o' | tail | awk '/:/{$4=""; print}' | open -ef
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key.
    The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
    A TextEdit window will open with the output of the command. Normally the command will produce no output, and the window will be empty. If the TextEdit window (not the Terminal window) has anything in it, stop here and post it — the text, please, not a screenshot. The title of the TextEdit window doesn't matter, and you don't need to post that.
    Step 2
    There are a few other possible causes of generalized slow performance that you can rule out easily.
    Disconnect all non-essential wired peripherals and remove aftermarket expansion cards, if any.
    Reset the System Management Controller.
    Run Software Update. If there's a firmware update, install it.
    If you're booting from an aftermarket SSD, see whether there's a firmware update for it.
    If you have a portable computer, check the cycle count of the battery. It may be due for replacement.
    If you have many image or video files on the Desktop with preview icons, move them to another folder.
    If applicable, uncheck all boxes in the iCloud preference pane. See whether there's any change.
    Check your keychains in Keychain Access for excessively duplicated items.
    Boot into Recovery mode, launch Disk Utility, and run Repair Disk.
    If you have a MacBook Pro with dual graphics, disable automatic graphics switching in the Energy Saverpreference pane for better performance at the cost of shorter battery life.
    Step 3
    When you notice the problem, launch the Activity Monitor application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Activity Monitor in the icon grid.
    Select the CPU tab of the Activity Monitor window.
    Select All Processes from the View menu or the menu in the toolbar, if not already selected.
    Click the heading of the % CPU column in the process table to sort the entries by CPU usage. You may have to click it twice to get the highest value at the top. What is it, and what is the process? Also post the values for User, System, and Idle at the bottom of the window.
    Select the Memory tab. What value is shown in the bottom part of the window for Swap used?
    Next, select the Disk tab. Post the approximate values shown for Reads in/sec and Writes out/sec (not Reads in andWrites out.)
    Step 4
    If you have more than one user account, you must be logged in as an administrator to carry out this step.
    Launch the Console application in the same way you launched Activity Monitor. Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Select the 50 or so most recent entries in the log. Copy them to the Clipboard by pressing the key combinationcommand-C. Paste into a reply to this message (command-V). You're looking for entries at the end of the log, not at the beginning.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Important: Some personal information, such as your name, may appear in the log. Anonymize before posting. That should be easy to do if your extract is not too long.

  • Why is aperture so slow

    for me aperture is slow to start, slow to operate and slow to shut down?  Am about ready to go back to iPhoto.

    In addition to the reasons Corky02 listed (how much RAM and what kind of processor do you have,BTW?) Aperture may become slow, if your hard drive fills up - keep more then 20% of your hard drive free.
    How long have you been using Aperture? If you are just starting to use Aperture and doing the initial setup of a large library, Aperture still may be busy with the initial processing of thousands of images. It will be much more responsive when this initial processing and indexing has been done.
    You may wish to turn on Aperture's  "Activity" viewer while you observing an an natural slowness - so you can see what tasks are performed and watch the progress. You also may pause tasks (indexing Faces, creation of previews), that you want to postpone and rather run over night. The Activity viewer can be started from Aperture's main Applications Window:
         Window -> Show Activity
    Two more diagnostic utilities (from Applications -> Utitilities) are useful: the "Console" and the "Activity Monitor". These will show you if any processes are crashing or logging diagnostic messages, and also how much processsing time Aperture  is using, or if other processes are competing with Aperture for processing time.
    Apart from the initial import of a large library Aperture may show slowness if you have a serious problem with your library:
    You may have imported a corrupted, incompatibable image
    or your library got corrupted (maybe by using a drive not formatted MAcOS X Extended, or by Force Quitting Aperture).
    Then the Aperture First Aid Tools may be able to fix this: Try to repair the permissions and to repair the library, as describe here:
         Aperture 3: Troubleshooting Basics: http://support.apple.com/kb/HT3805
    Report back, if this does not help.
    Regards
    Léonie

  • Aperture horribly slow on retina 16gb

    Since a few days i am using my new macbook pro retina i7 2.3 16gb ssd. and i am surprised how slow aperture is.
    i used it on a ssd macbookpro 13" i5 with 8gb for 2 years and always was ligtning fast.
    its not useable at all right now. when i scroll to photos (without preview mode) each photo takes up to 1/2 seconds which is just to slow. when i dodge and burn cursor gets choppy, and when i adjust levels it takes 2/3 sec to take any effect.
    Just noticed that when i only browse the cpu goes up to 113%+
    Since i just used it as temp library (later i will import that in my full archive) the library is only a 2.000 to 4.000 images large.
    Here some other information
    Macbook Pro 2.3 i7 16gb ram and 265GB SSD.
    Clean new install mountain lion (only adobe suite, chrome, aperture, dropbox and skype are installed)
    Turned off faces, and geo location in aperture, and also set previews to quality 6 and half size. no other apps running.
    by the way not only aperture gets slow, but when i just did some changes to a image and i command tab into a other app. its slow as well..
    getting crazy
    current activity monitor stats
    ram 12.7 gb used 3.2 free
    1.8 gb swap used
    disk activity small peaks of around 900kb so nothing exciting here
    network almost not used. (so no backup or anything is on
    for cpu with a idle aperture in the background is just normal
    93% idle
    skype uses some 3%
    chrome 2%
    photoshop 1.2%
    my other system is a i5 8gb macbook pro 13" with 8gb of ram and also a SSD and a lot of **** on it, and harddisk for 95% full and that one is lightning fast.
    so im really stuck here :-(

    I did a couple of things to resolve this issue and it was very succesful for me from what I can tell so far.I would like to share this information with everyone. For the record, I recently bought a standard MBP with the i7 2.6GHz CPU, discrete GT650M GPU with DDR5 1GB, and the Hi-Res AG screen. I dropped in 16GB RAM from Crucial and a Samsung 830 512GB SSD. So technically, my MBP with the exception of the retina screen should be pretty identical to the tech inside the rMBP. The SSD I installed also uses the same ATA controller as the Apple OEM NAND in the rMBP.
    Thanks to Linc Davis I used his suggestion to look for memory leaks within the Aperture application and my findings so far seem to dictate that he's probably right. I did some comparison with other editing software that I use and none of those exhibited the same behavior. The leaks detected with the "Aperture" process were exponentially higher than say "Photoshop" or "Elements." I think Apple has some code repair to do with Aperture. They rushed 64-bit and Retina support and somewhere the code got sloppy. As Linc also stated, it's tough to track a memory leak, but I find it strange that Aperture reports more leaks than other similar applications?
    After doing quite a bit of research, because I do like Aperture a lot as a workflow engine, I had to try my best to fix this. Personally, I don't think this has anything to do with our hardware. Everyone on this thread has the maximum amount of memory supported by their MBP's, so there's not much more that can be done here. Also, the rest of the tech is high-quality IMO. The problem I believe is the order that things have flowed with OSX updates, released, the most recent Aperture update, and the move to 64-bit forced by Mountain Lion. That said, here's what I suggest:
    Make sue that you have all of your updates for OSX, Aperture, and iPhoto if you're using a shared library.
    Backup your machine with TM. When this is done, moved on to #3.
    Download "Rember" and test your RAM just to make sure it passes all the checks.
    Check SMART status and make sure your SSD is not reporting any I/O errors. If all is good, continue.
    Download and install the latest version of ONYX 2.6.7.
    Using ONYX, go to the "Cleaning" tab and do a generic cleanup of all the crap on your machine.
    Using ONYX, go the "Maintenance" tab and repair permissions, run all the Scripts, and most important - rebuild Launch Services and the DYLD shared cache.
    Reboot your machine.
    Start Aperture holding down the OPTION and COMMAND keys. You will get prompted to REBUILD the database. Do this, not REPAIR (that does't really help). After the rebuild is complete, launch Aperture.
    Within Aperture, go into PREVIEWS tab, and set "Share previews with iLife and iWork" to NEVER.
    Go ahead and try... what do you think? For me, it runs much better, more reliable for sure.
    Now for the last and most controversial topic that has to do with TRIM. Problem is, people with an rMBP can't disable TRIM support on their SSD from what I can tell. Maybe I'm wrong? However, call me crazy, but when I had the TRIM hack enabled for my SSD, I saw some screwy things happening with I/O during Aperture use. According to everything I read from extremely knowledgeable people of the subject, TRIM is one of those uncertain grey areas. In theory the tech sounds logical, but in reality, I'm not sure if it's impacting I/O by making it unreliable? After all, those commands between the OS and the ATA controller have to be perfect in every way possible - otherwise it will create problems. In the case of Apple usage with there OEM NAND, it seems to be engineered. Can't say the same for Trim Enabler?? Just use caution IMO. Like I said, for me, I saw some weirdness, mainly beachballs. As soon as I disabled the TRIM patch, they went away. If you have a quality SSD like a Samsung or Intel, just rely on the firmware's GC. Do what I do, just let your system sit at the login prompt idle once a week.
    Another suggestion; use the PMSET command and change the default values for 'standbydelay" from 1600 to 86400 (24 hours). This will tell your MBP to stay in standby mode longer and only after 24 hours will it execute 'Standby' mode (which will write memory contents to the SSD - this just burns NAND P/E cycles unnecessarily). Don't know about you, but who the **** leaves their MBP in stanby mode for 30 days (based on Apple's logic)? I use it daily, so 24 hours fof sleep for me is fine. And, the MBP battery is great and can easily stay in sleep mode for at least 7 days untouched. Point is, less hibernation is better. The command is >>
    > sudo pmset -a standbydelay 86400
    Good luck!

Maybe you are looking for

  • I can't login from the desktop app - "Login error. Please contact the Admin."

    1) Does anyone have the same problem as described below? 2) Does anyone know how to fix it? When I try to "work online" from the desktop app, I get asked to log out of offline, then log into online. When I put in my username and password, it gives me

  • Display flash on webpage

    I have many pages with old object tags embedding flash movies. every time i open thse pages in dw cs3, it wants to convert them and says it will create the 2 .js files ac_activex.js and ac_runactivecontent.js The runactive file does reside in the scr

  • Problem with Yahoo mail after updating to 10.4.11

    I have recently updated to 10.4.11. After doing this, a change occurred when using my Yahoo Mail with Safari 3.0.4. Before the update, when typing in addresses in the "To" window when composing a message, Yahoo would fill in any recently used address

  • How do i put my ringtones off of itunes and on my iphone 4?

    i have 2 ringtones on my itunes and i have no idea how to transfer them to my phone. I've synced my phone but they're still not there.

  • Windows Server 2008 x64 and Crystal Reports Server Embedded

    We're attempting to certify our software with Windows Server 2008 x64 and want to know the best way to configure both the server and client of Crystal Reports Server Embedded.  Currently, our software is certified against Windows Server 2003 x86, and