4 Replies Latest reply: Feb 4, 2013 9:42 AM by Linc Davis
CyPsas Level 1 Level 1 (0 points)

I just installed the mountain lion on my macbook pro, lion had before, the team made ​​me very slow, when I play youtube or videos the videos are cut. The i7 processor and 4g memory I have. Believe it should work fine.

MacBook Pro, OS X Mountain Lion (10.8.2)
  • 1. Re: Mountain lion very slow
    macjack Level 9 Level 9 (50,510 points)

    What happens in a fresh user account or your Guest account, is the behavior the same?

  • 2. Re: Mountain lion very slow
    CyPsas Level 1 Level 1 (0 points)

    I have one account, that account happens to me, I have nothing. Another thing I notice is that it gets very hot but the team and I recently changed the fan, I mean you have to be working fine.

  • 3. Re: Mountain lion very slow
    macjack Level 9 Level 9 (50,510 points)

    So what you're saying is that you tested in another user and it is the same?


    How much available disk space do have left? If you're not running low on space then try a re-install the OS...

    Boot up holding command-r keys into your Recovery Volume.

    The screen should give you these choices...


    Restore from TM backup

    Reinstall Mac OS X

    Get help online

    Disk Utility


    First run Disk Utility Repair Disk, if you get errors run until no errors reported or reports "the disk cannot be fixed". Then, choose Reinstall OS X. This will be an install "in place" and shouldn't effect any of your own data or settings.

  • 4. Re: Mountain lion very slow
    Linc Davis Level 10 Level 10 (117,940 points)

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


    There are a few other possible causes of generalized slow performance that you can rule out easily.


    • 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.
    • Disconnect all non-essential wired peripherals and remove aftermarket expansion cards, if any.


    Otherwise, take the steps below when you notice the slowdown.


    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


    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.


    Select the 50 or so most recent entries in the log. Copy them to the Clipboard (command-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.