---
slug: "macbook-pro-intel-too-slow-after-standby"
title: "When Your MacBook Pro Intel Suddenly Slows Down (After Standby, etc.)"
description: "When an Intel MacBook Pro suddenly becomes slow after waking from standby, check and tune the `hibernate` / `standby` modes with `pmset`."
url: "https://www.ytyng.com/en/blog/macbook-pro-intel-too-slow-after-standby"
publish_date: "2021-08-26T10:48:03Z"
created: "2021-08-26T10:48:03Z"
updated: "2026-05-11T13:16:12.359Z"
categories: []
keywords: ""
featured_image_url: "https://media.ytyng.com/resize/20230812/95c5d90200114472a6afe859a905c0bc.png.webp?width=768"
has_video: false
has_music: false
video_urls: []
music_urls: []
lang: "en"
---

# When Your MacBook Pro Intel Suddenly Slows Down (After Standby, etc.)

<p>Cases where the MacBook Pro (Intel) suddenly slows down.</p>
<p>This often happened when recovering from standby mode.</p>
<p>The keyboard input becomes extremely sluggish, making it impractical to use.</p>
<p></p>
<p>Until now, I didn't know how to confirm this phenomenon, but it turns out that the CPU frequency of the Mac is being clocked down.</p>
<p>If you install an app called <a href="https://software.intel.com/content/www/us/en/develop/articles/intel-power-gadget.html" target="_blank">Intel Power Gadget</a>, you can see the CPU frequency and understand what's happening.</p>
<p>Normally, the CPU operates at 2.3 GHz, but under certain conditions, it starts running at a maximum of 0.7 GHz. When this happens, everything becomes sluggish, making it impractical to use.</p>
<p><br /><img src="/media/uploads/power-gadget/notification_center.png" alt="" width="349" height="678" /><br /><br /></p>
<p>This phenomenon cannot be resolved by a simple reboot; it requires clearing the SMC.</p>
<p>To clear the SMC, you need to turn off the power, then hold down the left Shift + left Control + left Option and the power button for 7 seconds.</p>
<p></p>
<p>This phenomenon has been occurring since I bought the MacBook Pro, and I didn't know what was happening, but I finally understood that it was a CPU clock down issue.</p>
<p>However, the conditions for its occurrence and how to avoid it are still unknown. For now, the only solution is to reset the SMC when it happens, which is quite troublesome.</p>
<p></p>