1 2 Previous Next 16 Replies Latest reply: Mar 6, 2013 2:47 PM by Linc Davis
cameronellis Level 1 Level 1 (0 points)

I got the bigger of the two options and the RAM upgrade.  A hard-won layout of $3k.  I got it so I could tear through Adobe CS6, yet it is slower than my Sony VAIO (which has a smaller processor and 1/4 the ram.)  It is slow even outside of CS6.  22GB took 1.5 hours to copy to a flash drive.  My old Dell desktop did it in 20 mins.  ***?  This *****.


MacBook Pro with Retina display, OS X Mountain Lion (10.8)
  • 1. Re: Why is my brand-new MacBookPro Retina so slow?
    John Galt Level 8 Level 8 (36,395 points)

    If you don't like it, return it for a refund. You have 14 calendar days. Enjoy your Sony.

  • 2. Re: Why is my brand-new MacBookPro Retina so slow?
    cameronellis Level 1 Level 1 (0 points)

    I might.  But first I would like to understand why this is happening.  Given the specs, I don't understand why it is so slow.  Are there settings I can fiddle with to make it faster?  Do I have a lemon?

  • 4. Re: Why is my brand-new MacBookPro Retina so slow?
    dbainbridge Level 1 Level 1 (115 points)

    Reset the SMC: http://support.apple.com/kb/HT3964?viewlocale=en_US&locale=en_US

     

    I copied 39GB over the thunderbolt to ethernet adapter in 10 min.

  • 5. Re: Why is my brand-new MacBookPro Retina so slow?
    cameronellis Level 1 Level 1 (0 points)

    OK, so how do I interpret the system menory panel...  how do I know when RAM and/or CPUs are maxed out?

  • 6. Re: Why is my brand-new MacBookPro Retina so slow?
    cameronellis Level 1 Level 1 (0 points)

    ah, but that's thunderbolt, not USB. Still, thanks for the comment, I'd like to interpret the memory stuff, then try resetting the SMC, to see if anything changes.

  • 7. Re: Why is my brand-new MacBookPro Retina so slow?
    dbainbridge Level 1 Level 1 (115 points)

    Reset the SMC first.  You should not be having memory issues with 16GB of RAM when machines with smaller amount work faster. 

  • 8. Re: Why is my brand-new MacBookPro Retina so slow?
    John Galt Level 8 Level 8 (36,395 points)

    cameronellis wrote:

     

    OK, so how do I interpret the system menory panel...  how do I know when RAM and/or CPUs are maxed out?

     

    here you go:

     

     

    Using Activity Monitor to read System Memory and determine how much RAM is being used

     

    The percent CPU load should be self-explanatory. You can select Window > Floating CPU Window to watch a graphical display that will remain on top of other windows, to monitor CPU load.

     

    I use Geekbench to compare systems to one another: http://www.primatelabs.com/geekbench/

  • 9. Re: Why is my brand-new MacBookPro Retina so slow?
    cameronellis Level 1 Level 1 (0 points)

    Resetting the SMC seemed to help a little bit, but still isn't the muscle book I thought was getting.  Could it have anything to do with my display?  I have it maxed out, (ie tiniest font)

  • 10. Re: Why is my brand-new MacBookPro Retina so slow?
    Linc Davis Level 10 Level 10 (118,330 points)

    First, back up all data immediately, as your boot drive might be failing.

     

    Take these steps when you notice the problem.

     

    Step 1

     

    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 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 System Memory tab. What values are shown in the bottom part of the window for Page outs and Swap used?

     

    Next, select the Disk Activity tab. Post the approximate values shown for Reads in/sec and Writes out/sec (not Reads in and Writes out.)

     

    Step 2

     

    You must be logged in as an administrator to carry out this step.

     

    Launch the Console application in the same way as above. 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.

     

    Post the 50 or so most recent messages in the log — the text, please, not a screenshot.

     

    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 a message.

    Important: Some personal information, such as your name, may appear in the log. Edit it out before posting.

  • 11. Re: Why is my brand-new MacBookPro Retina so slow?
    cameronellis Level 1 Level 1 (0 points)

    OK, thanks Linc

     

    Problems started again big time.  When I try to do anything in AE, such as thumb over to see a different frame, it takes forever to display.  So, the render process isn't super slow, it's just the AE interface.  To the point of making this computer useless for the purpose I bought it for. 

     

    ANY HELP WOULD BE SOOOOOO APPRECIATED.

     

    Here are my answers to your questions from the activity monitor, this is WHEN I try to do womething in AE:

    After Effects = 750% of the CPU

    User = ~95

    System = ~2

    Idle = ~3

     

    Page in = 763

    Page out = 0

     

    Reads in/sec = 0

    Reads out/sec = 0

    (but these jump around a bit, staying mostly around zero then jumping up to 2 or 17, etc)

     

    Here is the console log:

     

    3/6/13 3:01:26.670 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:01:40.670 PM WindowServer[72]: disable_update_likely_unbalanced: UI updates still disabled by application "Adobe After Effects 11.0" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

    3/6/13 3:02:04.504 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 38.84 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:02:47.712 PM CVMServer[104]: Check-in to the service com.apple.cvmsCompAgent_x86_64 failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.

    3/6/13 3:02:47.738 PM CVMServer[104]: Check-in to the service com.apple.cvmsCompAgent_x86_64 failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.

    3/6/13 3:03:20.617 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:03:21.427 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 1.81 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:04:56.096 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:05:10.096 PM WindowServer[72]: disable_update_likely_unbalanced: UI updates still disabled by application "Adobe After Effects 11.0" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

    3/6/13 3:05:35.695 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 40.60 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:05:50.459 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:06:04.460 PM WindowServer[72]: disable_update_likely_unbalanced: UI updates still disabled by application "Adobe After Effects 11.0" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

    3/6/13 3:06:16.918 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 27.46 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:07:16.107 PM mdworker[308]: Unable to talk to lsboxd

    3/6/13 3:07:16.157 PM sandboxd[310]: ([308]) mdworker(308) deny mach-lookup com.apple.ls.boxd

    3/6/13 3:07:16.000 PM kernel[0]: Sandbox: sandboxd(310) deny mach-lookup com.apple.coresymbolicationd

    3/6/13 3:08:18.270 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:08:32.270 PM WindowServer[72]: disable_update_likely_unbalanced: UI updates still disabled by application "Adobe After Effects 11.0" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

    3/6/13 3:08:36.751 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 19.48 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:08:56.496 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:08:56.911 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 1.42 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:09:04.695 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:09:11.992 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 8.30 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:10:00.861 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:10:14.861 PM WindowServer[72]: disable_update_likely_unbalanced: UI updates still disabled by application "Adobe After Effects 11.0" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

    3/6/13 3:10:17.096 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 17.24 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:11:39.958 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:11:53.958 PM WindowServer[72]: disable_update_likely_unbalanced: UI updates still disabled by application "Adobe After Effects 11.0" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

    3/6/13 3:12:01.086 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 22.13 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:12:19.136 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:12:32.818 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 14.68 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:12:54.529 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:12:55.986 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 2.46 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:14:03.928 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:14:17.928 PM WindowServer[72]: disable_update_likely_unbalanced: UI updates still disabled by application "Adobe After Effects 11.0" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

    3/6/13 3:14:29.551 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 26.63 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:16:10.896 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:16:12.035 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 2.14 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:16:13.080 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:16:17.289 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 5.21 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/6/13 3:16:54.568 PM WindowServer[72]: CGXDisableUpdate: UI updates were forcibly disabled by application "Adobe After Effects 11.0" for over 1.00 seconds. Server has re-enabled them.

    3/6/13 3:17:08.569 PM WindowServer[72]: disable_update_likely_unbalanced: UI updates still disabled by application "Adobe After Effects 11.0" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

    3/6/13 3:17:12.560 PM WindowServer[72]: reenable_update_for_connection: UI updates were finally reenabled by application "Adobe After Effects 11.0" after 18.99 seconds (server forcibly re-enabled them after 1.00 seconds)

     

    Thanks,

  • 12. Re: Why is my brand-new MacBookPro Retina so slow?
    Linc Davis Level 10 Level 10 (118,330 points)

    Quit After Effects, by force if necessary. It's causing the slowdown.

  • 13. Re: Why is my brand-new MacBookPro Retina so slow?
    cameronellis Level 1 Level 1 (0 points)

    Right.  But After Effects is the program I need to use!!

  • 14. Re: Why is my brand-new MacBookPro Retina so slow?
    Shootist007 Level 6 Level 6 (16,640 points)

    More then likely some type of software or hardware problem. Simply return it for a refund and either order another or something else. The one you have isn't right.

    cameronellis wrote:

     

    I might.  But first I would like to understand why this is happening.  Given the specs, I don't understand why it is so slow.  Are there settings I can fiddle with to make it faster?  Do I have a lemon?

1 2 Previous Next