Quick question about cores


Recommended Posts

Alright so I wanna know with my Mac if I can make it use all my cores since I have two?

For example in Windows(Vista..lets say); I type in msconfig and go to boot advanced settings.. I can then change how my computers boots using both cores instead of by default one..

Is there a way I can do that with Mac??

Link to comment
https://www.neowin.net/forum/topic/825930-quick-question-about-cores/
Share on other sites

The Mac takes full advantage of both cores in the background.

I use MenuMeters on my system and it shows both being utilized at the same time. What you can do is install the Processor Preference Pane Instructions Here...This will let you see both Cores as well as the utilization.

Alright so I wanna know with my Mac if I can make it use all my cores since I have two?

For example in Windows(Vista..lets say); I type in msconfig and go to boot advanced settings.. I can then change how my computers boots using both cores instead of by default one..

The whole premise is flawed.

The default is not 1. The default is grayed out, as in nothing picked, as in automatic. It is a debugging feature designed to reduce the number of processors. Manually setting it to the number you have won't make your system any faster. On the default settings, both cores will start almost immediately after you boot. Anyone who claims otherwise can show me screenshots of their boot progress in xperf, and I will eat my words.

Here is an example of the first few seconds of the boot process on a Core 2 Duo:

2qjg1t5.jpg

The red graph is the first core, while the blue is the second. If you look closely, you can see that the second core starts being used from about 0.8 seconds and out.

Edited by hdood
The Mac takes full advantage of both cores in the background.

I use MenuMeters on my system and it shows both being utilized at the same time. What you can do is install the Processor Preference Pane Instructions Here...This will let you see both Cores as well as the utilization.

Thank you

By the way, just to clear something up....the msconfig changes in Windows are so you can DISABLE a core during boot, not enable all during boot. By default, all cores are used during bootup.

Thanks for the info; was not to sure, just read on some tweak site to make it to the number of my cores..

The whole premise is flawed.

The default is not 1. The default is grayed out, as in nothing picked, as in automatic. It is a debugging feature designed to reduce the number of processors. Manually setting it to the number you have won't make your system any faster. On the default settings, both cores will start almost immediately after you boot. Anyone who claims otherwise can show me screenshots of their boot progress in xperf, and I will eat my words.

Ahh see I got confused then with the 1 greyed out.. I thought it was just using one..

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!