MacOS – Limit CPU when starting a task in terminal

You can try this.

You can use the Terminal Profiles to give each tab its own profile. This way, you can set the shell command for each tab individually.

And you can save the window group (tabs) so they will open on Terminal launch.

Example of set up

Set up your tabs in a window, i.e., cd to the directories in each tab as desired.

Then, go to the Terminal Preferences and to Settings Tab menu:

1. Select the Basic Profile.
2. Click the + button at the bottom. This will duplicate the profile.
3. Name the new profile (for example, home).

Repeat steps 1 - 3 as many times as the number of tabs, and name each of them with unique names.

In my example, I will have 'home' and 'work'.

Now, for my 'home' profile, I will:

4. Select the Shell tab.

5. Check 'Run command'.

6. Set the command string to cd ~

7. Check 'Run inside shell'.

For each profile, I will repeat steps 5 - 7, changing the cd command accordingly.

In my tab named 'Home Dir', I will:

1. Ctrl + click on the window to get the contextual menu, and select 'Show inspector'.
2. Select the 'settings' tab
3. Set its profile to the 'home' profile.

For each tab, I will repeat steps 1 - 3, changing the profile accordingly.

Now, my Home tab's profile should be the 'home' profile and my tab named 'Work Dir' profile should be the 'work' profile.

Now using the Windows Menu "Save Windows As Group".

Check the checkbox - "Use window group when Terminal starts".

I have tested it as best I can and this set up works.

Each tab opens in the cd's to its own directory. And does so on Terminal start up.

I like this so much, I am going to use it myself.

I found this for your reading pleasure:

Mavericks: Native CPU/IGPU Power Management

Native Mavericks power management delivers the best combination of processor and graphics performance and efficiency. The ingredients are an installed processor specific power management ssdt, a compatible system definition and the native power management kext. Native Mavericks power management does not require specific BIOS settings or anything more than one boot setting to load the power management ssdt. Credit for the technique described to PikeRAlpha.

What changed between Mountain Lion and Mavericks power management? The existing processor frequency/power state reporting tools (i.e., MSRDumper, HWMonitor) stopped reporting power states between idle and max non turbo. This led to an incorrect conclusion that native Mavericks power management was not working. A new tool, Intel Power Gadget, shows Mavericks power management is working as designed.

To be clear, native Mavericks power management is not mandatory. The consequences are not severe. Performance is similar, however, higher temps (~10 C), more power (5-10 W) and sleep problems are likely.

Change Log

v1.1 - 4/4/14 - CPU PM/Core i3/5/7 xxx (1st Generation)/Core 2 and earlier (below) v1.0 - 4/2/14: Initial Release

Requirements

OS X/10.9.2 or newer
    Desktop/Laptop only
    Server, see Guide: Asus X79 OS X Controlled SpeedStep

Stock Clock
    Verify
    OC, use ./ssdtPRGen.sh -f freq flag

Supported CPU/IGPU

Haswell/HD4600+ (Core i3/5/7 4xxx, 4th Generation)
Ivy Bridge/HD4000 (Core i3/5/7 3xxx, 3rd Generation)
Sandy Bridge/HD3000 (Core i3/5/7 2xxx, 2nd Generation)

Native Mavericks Power Management Recipe

System Definition - match processor generation/desktop or laptop
ssdt - custom to installed processor
kext - native IOPlatformPlugin.kext

Not considered

NullCPUPowerManagement.kext
Safe Mode boot (-x)
Discrete graphics