Thrum

Why is Logic Pro using so much CPU on my Mac?

Last reviewed: 19 November 2026.

Logic Pro has to calculate every software instrument and effect plug-in in real time, and a small I/O buffer size, which you want for recording, gives it less time to do so and raises the CPU load. Each track and its plug-ins are processed by a single thread, so one heavy live track can overload a core while others are idle. Raising the buffer size for mixing and freezing finished tracks are Apple's main ways to reduce the load.

How do you see Logic Pro's CPU load?

Activity Monitor shows Logic Pro's total CPU, but Logic Pro's own Performance Meter is more useful. Choose the Custom display option in the control bar to show the meter, which indicates the combined CPU load. Double-click it to open the Performance Meter window, which shows one meter per processing thread.

A single thread near the top while the others are low means one track (usually the selected or record-enabled one, with its plug-ins and any sends) is the bottleneck.

Why does a smaller buffer size use more CPU?

The I/O Buffer Size in Logic Pro > Settings > Audio > Devices sets how many samples Logic Pro processes at a time. Apple explains that reducing it lowers latency but places a higher strain on the processor; if it is too small for the Mac, you hear clicks, pops and crackles.

Apple's advice is to use the lowest buffer that does not crackle while recording, and the largest buffer while mixing so you can run more processor-intensive plug-ins. Tracks that are not live are processed ahead using the Process Buffer Range (Small 512, Medium 1024 or Large 2048 samples) without adding latency.

How do you reduce Logic Pro's CPU load?

  1. Raise the I/O buffer for mixing. Choose Logic Pro > Settings > Audio > Devices and pick a larger I/O Buffer Size. You can also show the buffer size in the control bar display to switch it quickly between recording and mixing.
  2. Freeze finished tracks. Click the Freeze button in a track header (show it via the track header components if it is hidden) and play the project. Source Only freezes the instrument without effects; Pre Fader includes the effects. A frozen track uses about as much processing as a plain audio track.
  3. Leave Processing Threads on Automatic. Apple recommends the Automatic setting unless you run other CPU-intensive apps alongside Logic Pro.
  4. Deselect the heaviest track when not recording. A selected or record-enabled track is live and processed on one thread with all its plug-ins; selecting a different track lets Logic Pro process the heavy one ahead of time.

When does Logic Pro's CPU use become a problem?

It is a problem when you hear clicks and dropouts, or Logic Pro stops playback with a system overload message. Watch the Performance Meter for one thread hitting the top, then freeze or simplify that track, or raise the buffer. A high overall CPU percentage in Activity Monitor during playback of a big project is normal; Logic Pro is designed to use the cores it has.

How can Thrum help with Logic Pro?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when Logic Pro is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click Logic Pro in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions

What buffer size should I use in Logic Pro?

Apple recommends the lowest I/O buffer size that plays without clicks while recording, and the largest size while mixing.

Does freezing a track change the sound?

No. Logic Pro bounces the track, including plug-ins and automation, to a file that plays in place of the original. Unfreeze it to make edits.

Sources