I'm running a MacBook Air M2 on **macOS Tahoe Beta 26.0 (developer beta 4, 25A5316i)** and have noticed a peculiar and aggressive thermal throttling behavior that makes the system very slow under sustained load. **The Problem:** When the machine's case gets hot, the system seems to enter a heavily throttled state. My monitoring app (Stats) shows that all **Performance cores are effectively shut down**: their utilization drops to 0% and their frequency is locked at the lowest state (660 MHz). This forces all system processes onto the **Efficiency cores**, which then run at 100% load. The computer becomes extremely sluggish and borderline unusable for anything beyond basic operations like text editing. Here is a screenshot of the system in this throttled state (Image 1): As you can see: * P-cores are at 0% usage and 660 MHz. * E-cores are at 100% usage. * The Average load is extremely high (68.48 over 1 minute). **The Paradox: It's Not Directly Tied to CPU Core Temperature** My initial assumption was that this was standard CPU thermal throttling. However, my observations show this is not the case. The throttling seems to be triggered by a different thermal sensor, not the CPU cores themselves. **Evidence 1: Throttling Occurs at Low CPU Temperatures** Here is a sensor reading from when the machine was in the throttled state described above. > Note: I don't know why the Stats app shows all cores as 'performance core' in this tab. * **Average CPU temperature is only 59.3°C**, and the hottest core is 61.2°C. These are very safe temperatures. * Despite the cool CPU, the P-cores are shut down as shown in the first image. **Evidence 2: No Throttling Occurs at High CPU Temperatures** Conversely, I can push the CPU to its thermal limit (e.g., with a short, intense task) without triggering this specific P-core shutdown, as long as the machine's chassis hasn't had time to heat soak. * Here, the **CPU cores are running at over 100°C** while the machine was still not throttled. * The CPU Power draw is high (14.53W) compared to the throttled state (0.16W), indicating the P-cores are active. * The system remains responsive during this time. This leads me to believe the throttling is a proactive measure based on a chassis, battery, or other component's temperature, rather than a reactive measure to the CPU's own temperature. **My Questions:** 1. What is the specific thermal management mechanism at play here? Is it a known behavior for fanless MacBooks to shut down P-cores? 2. Could this be a bug or an overly aggressive policy, possibly related to the macOS developer beta I am running? 3. Is there any way to adjust or disable this specific, preemptive throttling behavior? I understand the need for thermal management, but the current implementation makes the machine unusable long before the CPU itself is in any thermal danger.

I had my Mac M4 on sleep, as usual (macOS 15.5). Today when I opened it, it was warm. I took a look on the cpu usage I saw that it was walking up in around 1h intervals with a 15% user usage. When I opened it the cpu usage dropped and the machine cooled down. I would like to find what's the processes causing this usage as it don't seem right. Is it possible to find the logs of CPU usage % on a given time in the past? Or how to record CPU % usage per process (like as Activity monitor reports) in the future ? --- **Update**: I made a launchd script to dump 3 activity logs every 10minutes in a textfile. The process using resources is usually mediaanalysisd

2025-07-10 05:29:25
PID    COMMAND          %CPU TIME     #TH    #WQ     POWER
613    mediaanalysisd   79.6 04:01:30 7/1    4/1     79.6 
496    mds_stores       37.0 01:49:10 21/2   19/2    37.0 
3150   mediaanalysisd-a 6.9  24:47.90 15     14      6.9

There are whole industries founded on the use of Intel Intrinsics for CPU parallelisation (with SIMD). For example, the community of Lattice QCD physicists depend on that for boost in the efficiency of lattice simulations. Intel-based macs can be and are routinely used by such professionals to do their job. However, there are rumours about Apple replacing Intel CPU with ARM cpus in future Macs. Will these professionals have to replace Macs with other Intel-based computers, or are there alternatives to Intel Intrinsics for C that are supported on ARM-based CPUs?

Since my Macbook Pro (Big Sur 11.6) is burning through its battery power really quickly with mds_store clocking the most CPU usage, running the following command sudo fs_usage -w -f filesys mds_stores shows that /System/Volumes/VM/swapfile10 is commonly being used by mds_store. Running sudo fs_usage | grep /System/Volumes/VM/swapfile10 shows that this file is constantly being used by Brave Browser. However, when I tried to exclude /System/Volumes/VM/ from being indexed by Spotlight by going to System Preference > Spotlight > Privacy, I get a Privacy List Error, stating that > The item couldn't be added or removed because of an unknown error. How can we fix this and exclude the directory from Spotlight indexing?

I've looked around *a lot* to try to find the answer to this but have thus far been unsuccessful. I am programming in Python, and I have code that takes a long time to run (hours to months depending on the application) and I am trying to optimize it. On larger thread systems (once I get above ≈8 threads, but especially >18 threads), I run into a situation where the system is using up a large amount of my CPU instead of the actual code I want to run. On a 12-thread machine as I type this, the system is using ≈25–30% of my total CPU. If I try to run it on a 36-thread machine, the system takes >70% of the CPU which is simply unworkable (though running two instances of the code, limiting each to 18 threads, cuts this overhead back, oddly enough). The Activity Monitor indicates that

is using at least 10%, while

,

, and

are also using several percent, each (along with

at 1% so I should turn off Spotlight, and sometimes

spikes to >40%, but that's more rare ... note that that process is another launch system daemon). My older hypothesis was that it was a disk I/O issue, since the code was writing and reading many small files to try to keep track of certain things and recover if I needed to stop it. My now-working hypothesis, based on what I could find online about the interactions between

and

, is that this particular chunk of code is spawning a large number of processes and macOS's launching and security daemons are taking large amounts of CPU to make sure those processes are safe. These are things like calling "mv" and "rm" from the command line (os.system(...) in my Python code), and spawning other code that take a second or two to run (such as in a different conda environment when two have conflicting installs of necessary components). I count at least 40 potential spots where this chunk of code is possibly spawning child processes, and I thread it so that it's doing that concurrently however many threads there are (so, on a 12-thread machine, 12x40 over the course of ~10 seconds). It doesn't seem to me like this should be making my system take up so much CPU, but that's my best guess at the moment. Possibly related, the

is constantly spitting out to log files, "MacOS error: -67062", which again I've searched for and found no luck with diagnosing the issue. And,

is spawning a lot of "\\" messages in the Console, but its CPU% is around 0.3% so I'm less concerned about that. My apologies for rambling a bit here, but I'm trying to provide the information I have, and hopefully someone here has an idea. If I can get rid of this 25% or larger issue, that can save months of time. For what it's worth, I'm running macOS 10.14.5 and ..4 on two desktops, and 10.15.5 on a laptop. Same issue for all. Running in Linux on a nearly identical 36-thread system build does not have the overhead issue (but I really don't want to switch to Linux) which is another reason why I don't think it's a disk I/O problem.

I've seen some answers for this but it references older systems and older OSes. Can anyone update this for relevance in the Catalina era. I have a MacBook 10.1 with a shot battery. The screen is broken so I am using it strictly as a media/AirPlay server to my TV and have no plans to fix the battery whatsoever. I would really like to recover the performance on this. I have tried the remedies in other posts and the problem is there is no plist file with my MacBook model. One user mentioned letting the computer go into "default power saving mode naturally". But what does this mean? Can it be made into a script? Finally – I heard that w/o the battery GPU is also curtailed. Is that true and can there be a holistic fix for all of this?

I am aware of these answers: https://stackoverflow.com/questions/9948987/detect-current-cpu-clock-speed-programmatically-on-os-x https://apple.stackexchange.com/questions/97577/view-the-current-clock-speed-of-a-cpu-in-os-x Which refer to Intel Power Gadget as a way to obtain current CPU frequency, is there a program/method to obtain this information from the terminal? sysctl hw.cpufrequency only shows the nominal frequency of the CPU, i.e. what the manufacturer has stated. It does not consider Turbo Boost or lower frequencies when CPU is idle. (For example if CPU is i5, 1.4GHz, it will always state 1.4GHz) The C solution given it SO using sysctl.h has the same effect.

On Ventura 13.5.1 cloudd is using over 100% CPU constantly. The only way to stop it that I've discovered is to **reboot**, or to **log out of iCloud** in system settings. After logging in to iCloud again everything's fine, but as soon as I **launch Safari** cloudd will start doing the same thing again, and won't stop even after quitting Safari. Turning off specifically Safari for iCloud also seems to give the same result as logging out of iCloud completely. Launching other iCloud apps like Notes doesn't cause the same excessive surge for cloudd. I draw the conclusion that Safari iCloud integration is the cause. Looking in ~/Library/Containers/Safari/Data/CloudKit/ I see many small directories on the order of magnitude of MBs, while one is in the GBs: Is this normal and to be expected, or could it be indicative of a problem? I've already tried creating a **new local user account** to see if cloudd's behavior is repeated there. It is. That suggests that the problem is not due to some local accidental file structure problem, but more likely with the data synced from the cloud. Do these directories potentially conain data that has been synced from the cloud, thereby pointing to a possible cause (unending transfers)?

For the past couple of weeks, a process identified as usernoted appeared to "take over" my machine after a few hours of use, eating over 99% of available CPU. Force quitting the process doesn't help; only a system restart puts usernoted to sleep for a while. What is this process and how do I get it under control? I am running **OS X 10.10.5** (build 14F1021).

I have different machines running OSX 10.12 and 10.13, which use different processors. I am trying to get from terminal, a string that can show me which CPU instructions are supported by that machine; so I can use the appropriate software (some of the software require specific instructions to be present on the CPU, and if that CPU does not support them, the software will either work incorrectly or crash). I did check querying the system profiler via terminal but I can get only the CPU type and model, not the CPU instruction set that it support; and if I would do this by hand, getting every CPU model and checking online, it would take hours. * CPU instructions are these set of instructions like MMX, AVX, SSE; that allow your CPU to operate in a certain way. With years, they are added to the base CPU instruction set, so modern CPU these days support more than 15 different instruction types.

I am running VirtualBox VM 7.0.12 r159484 darwin.amd64 (Oct 12 2023 20:27:35) on Intel Mac Mini: Model Name: Mac mini Model Identifier: Macmini8,1 Processor Name: 6-Core Intel Core i5 Processor Speed: 3 GHz Number of Processors: 1 Total Number of Cores: 6 L2 Cache (per Core): 256 KB L3 Cache: 9 MB Memory: 8 GB System Firmware Version: 1968.140.7.0.0 (iBridge: 20.16.6072.0.0,0) OS Loader Version: 577.140.2~15 VirtualBox does not detect CPU virtualization extensions (VT-x) and the guest (32-bit Win XP) runs terribly slow. I think this is the relevant part of VBox.log: 00:00:00.322003 NEM: info: Found optional import Hypervisor!hv_capability. 00:00:00.322015 NEM: info: Found optional import Hypervisor!hv_vm_space_create. 00:00:00.322019 NEM: info: Found optional import Hypervisor!hv_vm_space_destroy. 00:00:00.322024 NEM: info: Found optional import Hypervisor!hv_vm_map_space. 00:00:00.322028 NEM: info: Found optional import Hypervisor!hv_vm_unmap_space. 00:00:00.322031 NEM: info: Found optional import Hypervisor!hv_vm_protect_space. 00:00:00.322036 NEM: info: Found optional import Hypervisor!hv_vcpu_set_space. 00:00:00.322043 NEM: info: Found optional import Hypervisor!hv_vcpu_run_until. 00:00:00.322047 NEM: info: Found optional import Hypervisor!hv_vcpu_get_exec_time. 00:00:00.322052 NEM: info: Found optional import Hypervisor!hv_vmx_vcpu_read_shadow_vmcs. 00:00:00.322056 NEM: info: Found optional import Hypervisor!hv_vmx_vcpu_write_shadow_vmcs. 00:00:00.322059 NEM: info: Found optional import Hypervisor!hv_vmx_vcpu_set_shadow_access. 00:00:00.322063 NEM: info: Found optional import Hypervisor!hv_vmx_get_msr_info. 00:00:00.322067 NEM: info: Found optional import Hypervisor!hv_vmx_vcpu_get_cap_write_vmcs. 00:00:00.322070 NEM: info: Found optional import Hypervisor!hv_vcpu_enable_managed_msr. 00:00:00.322074 NEM: info: Found optional import Hypervisor!hv_vcpu_set_msr_access. 00:00:00.322102 NEM: cMachTimePerNs=1 (TimeInfo.numer=1 TimeInfo.denom=1) 00:00:00.323768 NEM: Successfully created ASID: 1 00:00:00.323877 NEM: 00:00:00.323877 NEM: NEMR3Init: Turtle execution mode is active! 00:00:00.323878 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode. 00:00:00.323878 NEM: 00:00:00.323968 CPUM: No hardware-virtualization capability detected 00:00:00.324437 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x7 00:00:00.325550 CPUM: Matched host CPU INTEL 0x6/0x9e/0xa Intel_Core7_CoffeeLake with CPU DB entry 'Intel Core i7-6700K' (INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake) 00:00:00.325817 CPUM: MXCSR_MASK=0xffff (host: 0xffff) 00:00:00.325863 CPUM: Failed to query microcode revision. rc=VERR_SUP_DRIVERLESS 00:00:00.325923 CPUM: Changing leaf 13: EBX=0x340 -> 0x340, ECX=0x440 -> 0x340 00:00:00.325989 CPUM: MSR/CPUID reconciliation insert: 0x0000010b IA32_FLUSH_CMD 00:00:00.325995 CPUM: MSR/CPUID reconciliation insert: 0x0000010a IA32_ARCH_CAPABILITIES 00:00:00.326000 CPUM: MSR fudge: 0x00000001 IA32_P5_MC_TYPE 00:00:00.326004 CPUM: MSR fudge: 0x00000017 IA32_PLATFORM_ID 00:00:00.326007 CPUM: MSR fudge: 0x0000001b IA32_APIC_BASE 00:00:00.326011 CPUM: MSR fudge: 0x0000008b BIOS_SIGN 00:00:00.326014 CPUM: MSR fudge: 0x000000fe IA32_MTRRCAP 00:00:00.326018 CPUM: MSR fudge: 0x00000179 IA32_MCG_CAP 00:00:00.326021 CPUM: MSR fudge: 0x0000017a IA32_MCG_STATUS 00:00:00.326024 CPUM: MSR fudge: 0x000001a0 IA32_MISC_ENABLE 00:00:00.326028 CPUM: MSR fudge: 0x000001d9 IA32_DEBUGCTL 00:00:00.326031 CPUM: MSR fudge: 0x000001db P6_LAST_BRANCH_FROM_IP 00:00:00.326034 CPUM: MSR fudge: 0x000001dc P6_LAST_BRANCH_TO_IP 00:00:00.326038 CPUM: MSR fudge: 0x000001dd P6_LAST_INT_FROM_IP 00:00:00.326041 CPUM: MSR fudge: 0x000001de P6_LAST_INT_TO_IP 00:00:00.326044 CPUM: MSR fudge: 0x00000277 IA32_PAT 00:00:00.326048 CPUM: MSR fudge: 0x000002ff IA32_MTRR_DEF_TYPE 00:00:00.326051 CPUM: MSR fudge: 0x00000400 IA32_MCi_CTL_STATUS_ADDR_MISC 00:00:00.326069 CPUM: MSR fudge: 0xc0000103 AMD64_TSC_AUX 00:00:00.326073 CPUM: MSR fudge: 0x00000122 IA32_TSX_CTRL 00:00:00.326131 CPUM: SetGuestCpuIdFeature: Enabled PAE 00:00:00.326242 NEM: VMX_VMCS32_CTRL_PIN_EXEC = (allowed_0=0x00003f allowed_1=0x00007f) 00:00:00.326251 NEM: Bit 00 = MUST be set 00:00:00.326255 NEM: Bit 01 = MUST be set 00:00:00.326258 NEM: Bit 02 = MUST be set 00:00:00.326261 NEM: Bit 03 = MUST be set 00:00:00.326264 NEM: Bit 04 = MUST be set 00:00:00.326268 NEM: Bit 05 = MUST be set 00:00:00.326271 NEM: Bit 06 = Can be set or not be set 00:00:00.326274 NEM: Bit 07 = Must NOT be set 00:00:00.326277 NEM: Bit 08 = Must NOT be set 00:00:00.326281 NEM: Bit 09 = Must NOT be set 00:00:00.326284 NEM: Bit 10 = Must NOT be set 00:00:00.326287 NEM: Bit 11 = Must NOT be set 00:00:00.326290 NEM: Bit 12 = Must NOT be set 00:00:00.326293 NEM: Bit 13 = Must NOT be set 00:00:00.326297 NEM: Bit 14 = Must NOT be set 00:00:00.326300 NEM: Bit 15 = Must NOT be set 00:00:00.326303 NEM: Bit 16 = Must NOT be set 00:00:00.326306 NEM: Bit 17 = Must NOT be set 00:00:00.326309 NEM: Bit 18 = Must NOT be set 00:00:00.326313 NEM: Bit 19 = Must NOT be set 00:00:00.326316 NEM: Bit 20 = Must NOT be set 00:00:00.326319 NEM: Bit 21 = Must NOT be set 00:00:00.326322 NEM: Bit 22 = Must NOT be set 00:00:00.326325 NEM: Bit 23 = Must NOT be set 00:00:00.326329 NEM: Bit 24 = Must NOT be set 00:00:00.326332 NEM: Bit 25 = Must NOT be set 00:00:00.326335 NEM: Bit 26 = Must NOT be set 00:00:00.326338 NEM: Bit 27 = Must NOT be set 00:00:00.326341 NEM: Bit 28 = Must NOT be set 00:00:00.326345 NEM: Bit 29 = Must NOT be set 00:00:00.326348 NEM: Bit 30 = Must NOT be set 00:00:00.326351 NEM: Bit 31 = Must NOT be set 00:00:00.326355 NEM: VMX_VMCS32_CTRL_PROC_EXEC = (allowed_0=0x9500697a allowed_1=0xfdf9fffe) 00:00:00.326359 NEM: Bit 00 = Must NOT be set 00:00:00.326362 NEM: Bit 01 = MUST be set 00:00:00.326365 NEM: Bit 02 = Can be set or not be set 00:00:00.326368 NEM: Bit 03 = MUST be set 00:00:00.326372 NEM: Bit 04 = MUST be set 00:00:00.326375 NEM: Bit 05 = MUST be set 00:00:00.326378 NEM: Bit 06 = MUST be set 00:00:00.326381 NEM: Bit 07 = Can be set or not be set 00:00:00.326384 NEM: Bit 08 = MUST be set 00:00:00.326387 NEM: Bit 09 = Can be set or not be set 00:00:00.326391 NEM: Bit 10 = Can be set or not be set 00:00:00.326394 NEM: Bit 11 = MUST be set 00:00:00.326397 NEM: Bit 12 = Can be set or not be set 00:00:00.326400 NEM: Bit 13 = MUST be set 00:00:00.326404 NEM: Bit 14 = MUST be set 00:00:00.326407 NEM: Bit 15 = Can be set or not be set 00:00:00.326410 NEM: Bit 16 = Can be set or not be set 00:00:00.326413 NEM: Bit 17 = Must NOT be set 00:00:00.326416 NEM: Bit 18 = Must NOT be set 00:00:00.326420 NEM: Bit 19 = Can be set or not be set 00:00:00.326423 NEM: Bit 20 = Can be set or not be set 00:00:00.326426 NEM: Bit 21 = Can be set or not be set 00:00:00.326429 NEM: Bit 22 = Can be set or not be set 00:00:00.326432 NEM: Bit 23 = Can be set or not be set 00:00:00.326435 NEM: Bit 24 = MUST be set 00:00:00.326439 NEM: Bit 25 = Must NOT be set 00:00:00.326442 NEM: Bit 26 = MUST be set 00:00:00.326445 NEM: Bit 27 = Can be set or not be set 00:00:00.326448 NEM: Bit 28 = MUST be set 00:00:00.326451 NEM: Bit 29 = Can be set or not be set 00:00:00.326455 NEM: Bit 30 = Can be set or not be set 00:00:00.326458 NEM: Bit 31 = MUST be set 00:00:00.326461 NEM: VMX_VMCS32_CTRL_EXCEPTION_BITMAP = (allowed_0=0x000000 allowed_1=0xffffffff) 00:00:00.326465 NEM: Bit 00 = Can be set or not be set 00:00:00.326468 NEM: Bit 01 = Can be set or not be set 00:00:00.326481 NEM: Bit 02 = Can be set or not be set 00:00:00.326484 NEM: Bit 03 = Can be set or not be set 00:00:00.326488 NEM: Bit 04 = Can be set or not be set 00:00:00.326491 NEM: Bit 05 = Can be set or not be set 00:00:00.326494 NEM: Bit 06 = Can be set or not be set 00:00:00.326497 NEM: Bit 07 = Can be set or not be set 00:00:00.326503 NEM: Bit 08 = Can be set or not be set 00:00:00.326506 NEM: Bit 09 = Can be set or not be set 00:00:00.326509 NEM: Bit 10 = Can be set or not be set 00:00:00.326513 NEM: Bit 11 = Can be set or not be set 00:00:00.326516 NEM: Bit 12 = Can be set or not be set 00:00:00.326519 NEM: Bit 13 = Can be set or not be set 00:00:00.326522 NEM: Bit 14 = Can be set or not be set 00:00:00.326525 NEM: Bit 15 = Can be set or not be set 00:00:00.326529 NEM: Bit 16 = Can be set or not be set 00:00:00.326553 NEM: Bit 17 = Can be set or not be set 00:00:00.326556 NEM: Bit 18 = Can be set or not be set 00:00:00.326559 NEM: Bit 19 = Can be set or not be set 00:00:00.326562 NEM: Bit 20 = Can be set or not be set 00:00:00.326565 NEM: Bit 21 = Can be set or not be set 00:00:00.326568 NEM: Bit 22 = Can be set or not be set 00:00:00.326571 NEM: Bit 23 = Can be set or not be set 00:00:00.326573 NEM: Bit 24 = Can be set or not be set 00:00:00.326576 NEM: Bit 25 = Can be set or not be set 00:00:00.326579 NEM: Bit 26 = Can be set or not be set 00:00:00.326582 NEM: Bit 27 = Can be set or not be set 00:00:00.326585 NEM: Bit 28 = Can be set or not be set 00:00:00.326588 NEM: Bit 29 = Can be set or not be set 00:00:00.326591 NEM: Bit 30 = Can be set or not be set 00:00:00.326594 NEM: Bit 31 = Can be set or not be set 00:00:00.326598 NEM: VMX_VMCS32_CTRL_EXIT = (allowed_0=0x236fff allowed_1=0x737fff) 00:00:00.326601 NEM: Bit 00 = MUST be set 00:00:00.326604 NEM: Bit 01 = MUST be set 00:00:00.326607 NEM: Bit 02 = MUST be set 00:00:00.326610 NEM: Bit 03 = MUST be set 00:00:00.326613 NEM: Bit 04 = MUST be set 00:00:00.326616 NEM: Bit 05 = MUST be set 00:00:00.326619 NEM: Bit 06 = MUST be set 00:00:00.326622 NEM: Bit 07 = MUST be set 00:00:00.326625 NEM: Bit 08 = MUST be set 00:00:00.326627 NEM: Bit 09 = MUST be set 00:00:00.326630 NEM: Bit 10 = MUST be set 00:00:00.326633 NEM: Bit 11 = MUST be set 00:00:00.326636 NEM: Bit 12 = Can be set or not be set 00:00:00.326639 NEM: Bit 13 = MUST be set 00:00:00.326642 NEM: Bit 14 = MUST be set 00:00:00.326645 NEM: Bit 15 = Must NOT be set 00:00:00.326648 NEM: Bit 16 = MUST be set 00:00:00.326651 NEM: Bit 17 = MUST be set 00:00:00.326654 NEM: Bit 18 = Must NOT be set 00:00:00.326657 NEM: Bit 19 = Must NOT be set 00:00:00.326660 NEM: Bit 20 = Can be set or not be set 00:00:00.326663 NEM: Bit 21 = MUST be set 00:00:00.326666 NEM: Bit 22 = Can be set or not be set 00:00:00.326669 NEM: Bit 23 = Must NOT be set 00:00:00.326672 NEM: Bit 24 = Must NOT be set 00:00:00.326674 NEM: Bit 25 = Must NOT be set 00:00:00.326677 NEM: Bit 26 = Must NOT be set 00:00:00.326680 NEM: Bit 27 = Must NOT be set 00:00:00.326683 NEM: Bit 28 = Must NOT be set 00:00:00.326686 NEM: Bit 29 = Must NOT be set 00:00:00.326689 NEM: Bit 30 = Must NOT be set 00:00:00.326692 NEM: Bit 31 = Must NOT be set 00:00:00.326695 NEM: VMX_VMCS32_CTRL_ENTRY = (allowed_0=0x0091ff allowed_1=0x00b3ff) 00:00:00.326699 NEM: Bit 00 = MUST be set 00:00:00.326702 NEM: Bit 01 = MUST be set 00:00:00.326705 NEM: Bit 02 = MUST be set 00:00:00.326708 NEM: Bit 03 = MUST be set 00:00:00.326711 NEM: Bit 04 = MUST be set 00:00:00.326714 NEM: Bit 05 = MUST be set 00:00:00.326717 NEM: Bit 06 = MUST be set 00:00:00.326720 NEM: Bit 07 = MUST be set 00:00:00.326729 NEM: Bit 08 = MUST be set 00:00:00.326732 NEM: Bit 09 = Can be set or not be set 00:00:00.326735 NEM: Bit 10 = Must NOT be set 00:00:00.326738 NEM: Bit 11 = Must NOT be set 00:00:00.326741 NEM: Bit 12 = MUST be set 00:00:00.326744 NEM: Bit 13 = Can be set or not be set 00:00:00.326747 NEM: Bit 14 = Must NOT be set 00:00:00.326750 NEM: Bit 15 = MUST be set 00:00:00.326753 NEM: Bit 16 = Must NOT be set 00:00:00.326755 NEM: Bit 17 = Must NOT be set 00:00:00.326758 NEM: Bit 18 = Must NOT be set 00:00:00.326761 NEM: Bit 19 = Must NOT be set 00:00:00.326764 NEM: Bit 20 = Must NOT be set 00:00:00.326767 NEM: Bit 21 = Must NOT be set 00:00:00.326770 NEM: Bit 22 = Must NOT be set 00:00:00.326773 NEM: Bit 23 = Must NOT be set 00:00:00.326776 NEM: Bit 24 = Must NOT be set 00:00:00.326779 NEM: Bit 25 = Must NOT be set 00:00:00.326782 NEM: Bit 26 = Must NOT be set 00:00:00.326784 NEM: Bit 27 = Must NOT be set 00:00:00.326787 NEM: Bit 28 = Must NOT be set 00:00:00.326790 NEM: Bit 29 = Must NOT be set 00:00:00.326793 NEM: Bit 30 = Must NOT be set 00:00:00.326796 NEM: Bit 31 = Must NOT be set 00:00:00.326799 NEM: VMX_VMCS32_CTRL_PROC_EXEC2 = (allowed_0=0x0000a2 allowed_1=0x515cef) 00:00:00.326803 NEM: Bit 00 = Can be set or not be set 00:00:00.326806 NEM: Bit 01 = MUST be set 00:00:00.326809 NEM: Bit 02 = Can be set or not be set 00:00:00.326812 NEM: Bit 03 = Can be set or not be set 00:00:00.326815 NEM: Bit 04 = Must NOT be set 00:00:00.326818 NEM: Bit 05 = MUST be set 00:00:00.326820 NEM: Bit 06 = Can be set or not be set 00:00:00.326823 NEM: Bit 07 = MUST be set 00:00:00.326826 NEM: Bit 08 = Must NOT be set 00:00:00.326829 NEM: Bit 09 = Must NOT be set 00:00:00.326832 NEM: Bit 10 = Can be set or not be set 00:00:00.326835 NEM: Bit 11 = Can be set or not be set 00:00:00.326838 NEM: Bit 12 = Can be set or not be set 00:00:00.326841 NEM: Bit 13 = Must NOT be set 00:00:00.326844 NEM: Bit 14 = Can be set or not be set 00:00:00.326847 NEM: Bit 15 = Must NOT be set 00:00:00.326850 NEM: Bit 16 = Can be set or not be set 00:00:00.326853 NEM: Bit 17 = Must NOT be set 00:00:00.326856 NEM: Bit 18 = Must NOT be set 00:00:00.326859 NEM: Bit 19 = Must NOT be set 00:00:00.326862 NEM: Bit 20 = Can be set or not be set 00:00:00.326864 NEM: Bit 21 = Must NOT be set 00:00:00.326867 NEM: Bit 22 = Can be set or not be set 00:00:00.326870 NEM: Bit 23 = Must NOT be set 00:00:00.326873 NEM: Bit 24 = Must NOT be set 00:00:00.326876 NEM: Bit 25 = Must NOT be set 00:00:00.326879 NEM: Bit 26 = Must NOT be set 00:00:00.326882 NEM: Bit 27 = Must NOT be set 00:00:00.326885 NEM: Bit 28 = Must NOT be set 00:00:00.326888 NEM: Bit 29 = Must NOT be set 00:00:00.326891 NEM: Bit 30 = Must NOT be set 00:00:00.326894 NEM: Bit 31 = Must NOT be set 00:00:00.326897 NEM: VMX_VMCS32_CTRL_PLE_GAP = (allowed_0=0x000000 allowed_1=0xffffffff) 00:00:00.326900 NEM: Bit 00 = Can be set or not be set 00:00:00.326903 NEM: Bit 01 = Can be set or not be set 00:00:00.326906 NEM: Bit 02 = Can be set or not be set 00:00:00.326909 NEM: Bit 03 = Can be set or not be set 00:00:00.326912 NEM: Bit 04 = Can be set or not be set 00:00:00.326915 NEM: Bit 05 = Can be set or not be set 00:00:00.326918 NEM: Bit 06 = Can be set or not be set 00:00:00.326921 NEM: Bit 07 = Can be set or not be set 00:00:00.326924 NEM: Bit 08 = Can be set or not be set 00:00:00.326927 NEM: Bit 09 = Can be set or not be set 00:00:00.326930 NEM: Bit 10 = Can be set or not be set 00:00:00.326932 NEM: Bit 11 = Can be set or not be set 00:00:00.326935 NEM: Bit 12 = Can be set or not be set 00:00:00.326938 NEM: Bit 13 = Can be set or not be set 00:00:00.326947 NEM: Bit 14 = Can be set or not be set 00:00:00.326950 NEM: Bit 15 = Can be set or not be set 00:00:00.326953 NEM: Bit 16 = Can be set or not be set 00:00:00.326956 NEM: Bit 17 = Can be set or not be set 00:00:00.326959 NEM: Bit 18 = Can be set or not be set 00:00:00.326962 NEM: Bit 19 = Can be set or not be set 00:00:00.326965 NEM: Bit 20 = Can be set or not be set 00:00:00.326968 NEM: Bit 21 = Can be set or not be set 00:00:00.326971 NEM: Bit 22 = Can be set or not be set 00:00:00.326974 NEM: Bit 23 = Can be set or not be set 00:00:00.326976 NEM: Bit 24 = Can be set or not be set 00:00:00.326979 NEM: Bit 25 = Can be set or not be set 00:00:00.326982 NEM: Bit 26 = Can be set or not be set 00:00:00.326985 NEM: Bit 27 = Can be set or not be set 00:00:00.326988 NEM: Bit 28 = Can be set or not be set 00:00:00.326991 NEM: Bit 29 = Can be set or not be set 00:00:00.326994 NEM: Bit 30 = Can be set or not be set 00:00:00.326997 NEM: Bit 31 = Can be set or not be set 00:00:00.327000 NEM: VMX_VMCS32_CTRL_PLE_WINDOW = (allowed_0=0x000000 allowed_1=0xffffffff) 00:00:00.327003 NEM: Bit 00 = Can be set or not be set 00:00:00.327006 NEM: Bit 01 = Can be set or not be set 00:00:00.327009 NEM: Bit 02 = Can be set or not be set 00:00:00.327012 NEM: Bit 03 = Can be set or not be set 00:00:00.327015 NEM: Bit 04 = Can be set or not be set 00:00:00.327018 NEM: Bit 05 = Can be set or not be set 00:00:00.327021 NEM: Bit 06 = Can be set or not be set 00:00:00.327024 NEM: Bit 07 = Can be set or not be set 00:00:00.327026 NEM: Bit 08 = Can be set or not be set 00:00:00.327029 NEM: Bit 09 = Can be set or not be set 00:00:00.327032 NEM: Bit 10 = Can be set or not be set 00:00:00.327035 NEM: Bit 11 = Can be set or not be set 00:00:00.327038 NEM: Bit 12 = Can be set or not be set 00:00:00.327041 NEM: Bit 13 = Can be set or not be set 00:00:00.327044 NEM: Bit 14 = Can be set or not be set 00:00:00.327047 NEM: Bit 15 = Can be set or not be set 00:00:00.327050 NEM: Bit 16 = Can be set or not be set 00:00:00.327053 NEM: Bit 17 = Can be set or not be set 00:00:00.327055 NEM: Bit 18 = Can be set or not be set 00:00:00.327058 NEM: Bit 19 = Can be set or not be set 00:00:00.327061 NEM: Bit 20 = Can be set or not be set 00:00:00.327064 NEM: Bit 21 = Can be set or not be set 00:00:00.327067 NEM: Bit 22 = Can be set or not be set 00:00:00.327070 NEM: Bit 23 = Can be set or not be set 00:00:00.327073 NEM: Bit 24 = Can be set or not be set 00:00:00.327076 NEM: Bit 25 = Can be set or not be set 00:00:00.327078 NEM: Bit 26 = Can be set or not be set 00:00:00.327081 NEM: Bit 27 = Can be set or not be set 00:00:00.327084 NEM: Bit 28 = Can be set or not be set 00:00:00.327087 NEM: Bit 29 = Can be set or not be set 00:00:00.327090 NEM: Bit 30 = Can be set or not be set 00:00:00.327093 NEM: Bit 31 = Can be set or not be set 00:00:00.327096 NEM: VMX_VMCS64_CTRL_TSC_OFFSET_FULL = (allowed_0=0xffffffffffffffff allowed_1=0x00000000000000) 00:00:00.327100 NEM: Bit 00 = UNDEFINED (AppleHV error)! 00:00:00.327103 NEM: Bit 01 = UNDEFINED (AppleHV error)! 00:00:00.327106 NEM: Bit 02 = UNDEFINED (AppleHV error)! 00:00:00.327109 NEM: Bit 03 = UNDEFINED (AppleHV error)! 00:00:00.327112 NEM: Bit 04 = UNDEFINED (AppleHV error)! 00:00:00.327115 NEM: Bit 05 = UNDEFINED (AppleHV error)! 00:00:00.327118 NEM: Bit 06 = UNDEFINED (AppleHV error)! 00:00:00.327121 NEM: Bit 07 = UNDEFINED (AppleHV error)! 00:00:00.327124 NEM: Bit 08 = UNDEFINED (AppleHV error)! 00:00:00.327127 NEM: Bit 09 = UNDEFINED (AppleHV error)! 00:00:00.327129 NEM: Bit 10 = UNDEFINED (AppleHV error)! 00:00:00.327132 NEM: Bit 11 = UNDEFINED (AppleHV error)! 00:00:00.327141 NEM: Bit 12 = UNDEFINED (AppleHV error)! 00:00:00.327145 NEM: Bit 13 = UNDEFINED (AppleHV error)! 00:00:00.327148 NEM: Bit 14 = UNDEFINED (AppleHV error)! 00:00:00.327150 NEM: Bit 15 = UNDEFINED (AppleHV error)! 00:00:00.327153 NEM: Bit 16 = UNDEFINED (AppleHV error)! 00:00:00.327156 NEM: Bit 17 = UNDEFINED (AppleHV error)! 00:00:00.327159 NEM: Bit 18 = UNDEFINED (AppleHV error)! 00:00:00.327162 NEM: Bit 19 = UNDEFINED (AppleHV error)! 00:00:00.327165 NEM: Bit 20 = UNDEFINED (AppleHV error)! 00:00:00.327168 NEM: Bit 21 = UNDEFINED (AppleHV error)! 00:00:00.327171 NEM: Bit 22 = UNDEFINED (AppleHV error)! 00:00:00.327174 NEM: Bit 23 = UNDEFINED (AppleHV error)! 00:00:00.327177 NEM: Bit 24 = UNDEFINED (AppleHV error)! 00:00:00.327180 NEM: Bit 25 = UNDEFINED (AppleHV error)! 00:00:00.327183 NEM: Bit 26 = UNDEFINED (AppleHV error)! 00:00:00.327185 NEM: Bit 27 = UNDEFINED (AppleHV error)! 00:00:00.327188 NEM: Bit 28 = UNDEFINED (AppleHV error)! 00:00:00.327191 NEM: Bit 29 = UNDEFINED (AppleHV error)! 00:00:00.327194 NEM: Bit 30 = UNDEFINED (AppleHV error)! 00:00:00.327197 NEM: Bit 31 = UNDEFINED (AppleHV error)! 00:00:00.327200 NEM: Bit 32 = UNDEFINED (AppleHV error)! 00:00:00.327203 NEM: Bit 33 = UNDEFINED (AppleHV error)! 00:00:00.327206 NEM: Bit 34 = UNDEFINED (AppleHV error)! 00:00:00.327209 NEM: Bit 35 = UNDEFINED (AppleHV error)! 00:00:00.327212 NEM: Bit 36 = UNDEFINED (AppleHV error)! 00:00:00.327215 NEM: Bit 37 = UNDEFINED (AppleHV error)! 00:00:00.327217 NEM: Bit 38 = UNDEFINED (AppleHV error)! 00:00:00.327220 NEM: Bit 39 = UNDEFINED (AppleHV error)! 00:00:00.327223 NEM: Bit 40 = UNDEFINED (AppleHV error)! 00:00:00.327226 NEM: Bit 41 = UNDEFINED (AppleHV error)! 00:00:00.327229 NEM: Bit 42 = UNDEFINED (AppleHV error)! 00:00:00.327232 NEM: Bit 43 = UNDEFINED (AppleHV error)! 00:00:00.327235 NEM: Bit 44 = UNDEFINED (AppleHV error)! 00:00:00.327238 NEM: Bit 45 = UNDEFINED (AppleHV error)! 00:00:00.327241 NEM: Bit 46 = UNDEFINED (AppleHV error)! 00:00:00.327244 NEM: Bit 47 = UNDEFINED (AppleHV error)! 00:00:00.327246 NEM: Bit 48 = UNDEFINED (AppleHV error)! 00:00:00.327249 NEM: Bit 49 = UNDEFINED (AppleHV error)! 00:00:00.327252 NEM: Bit 50 = UNDEFINED (AppleHV error)! 00:00:00.327255 NEM: Bit 51 = UNDEFINED (AppleHV error)! 00:00:00.327258 NEM: Bit 52 = UNDEFINED (AppleHV error)! 00:00:00.327261 NEM: Bit 53 = UNDEFINED (AppleHV error)! 00:00:00.327264 NEM: Bit 54 = UNDEFINED (AppleHV error)! 00:00:00.327267 NEM: Bit 55 = UNDEFINED (AppleHV error)! 00:00:00.327270 NEM: Bit 56 = UNDEFINED (AppleHV error)! 00:00:00.327273 NEM: Bit 57 = UNDEFINED (AppleHV error)! 00:00:00.327276 NEM: Bit 58 = UNDEFINED (AppleHV error)! 00:00:00.327278 NEM: Bit 59 = UNDEFINED (AppleHV error)! 00:00:00.327281 NEM: Bit 60 = UNDEFINED (AppleHV error)! 00:00:00.327284 NEM: Bit 61 = UNDEFINED (AppleHV error)! 00:00:00.327287 NEM: Bit 62 = UNDEFINED (AppleHV error)! 00:00:00.327290 NEM: Bit 63 = UNDEFINED (AppleHV error)! 00:00:00.327293 NEM: VMX_VMCS64_GUEST_DEBUGCTL_FULL = (allowed_0=0xffffffffffffffff allowed_1=0x00000000009803) 00:00:00.327297 NEM: Bit 00 = MUST be set 00:00:00.327300 NEM: Bit 01 = MUST be set 00:00:00.327303 NEM: Bit 02 = UNDEFINED (AppleHV error)! 00:00:00.327306 NEM: Bit 03 = UNDEFINED (AppleHV error)! 00:00:00.327309 NEM: Bit 04 = UNDEFINED (AppleHV error)! 00:00:00.327312 NEM: Bit 05 = UNDEFINED (AppleHV error)! 00:00:00.327315 NEM: Bit 06 = UNDEFINED (AppleHV error)! 00:00:00.327318 NEM: Bit 07 = UNDEFINED (AppleHV error)! 00:00:00.327320 NEM: Bit 08 = UNDEFINED (AppleHV error)! 00:00:00.327323 NEM: Bit 09 = UNDEFINED (AppleHV error)! 00:00:00.327326 NEM: Bit 10 = UNDEFINED (AppleHV error)! 00:00:00.327335 NEM: Bit 11 = MUST be set 00:00:00.327338 NEM: Bit 12 = MUST be set 00:00:00.327341 NEM: Bit 13 = UNDEFINED (AppleHV error)! 00:00:00.327344 NEM: Bit 14 = UNDEFINED (AppleHV error)! 00:00:00.327347 NEM: Bit 15 = MUST be set 00:00:00.327350 NEM: Bit 16 = UNDEFINED (AppleHV error)! 00:00:00.327353 NEM: Bit 17 = UNDEFINED (AppleHV error)! 00:00:00.327356 NEM: Bit 18 = UNDEFINED (AppleHV error)! 00:00:00.327359 NEM: Bit 19 = UNDEFINED (AppleHV error)! 00:00:00.327362 NEM: Bit 20 = UNDEFINED (AppleHV error)! 00:00:00.327365 NEM: Bit 21 = UNDEFINED (AppleHV error)! 00:00:00.327368 NEM: Bit 22 = UNDEFINED (AppleHV error)! 00:00:00.327371 NEM: Bit 23 = UNDEFINED (AppleHV error)! 00:00:00.327373 NEM: Bit 24 = UNDEFINED (AppleHV error)! 00:00:00.327376 NEM: Bit 25 = UNDEFINED (AppleHV error)! 00:00:00.327379 NEM: Bit 26 = UNDEFINED (AppleHV error)! 00:00:00.327382 NEM: Bit 27 = UNDEFINED (AppleHV error)! 00:00:00.327385 NEM: Bit 28 = UNDEFINED (AppleHV error)! 00:00:00.327388 NEM: Bit 29 = UNDEFINED (AppleHV error)! 00:00:00.327391 NEM: Bit 30 = UNDEFINED (AppleHV error)! 00:00:00.327394 NEM: Bit 31 = UNDEFINED (AppleHV error)! 00:00:00.327397 NEM: Bit 32 = UNDEFINED (AppleHV error)! 00:00:00.327400 NEM: Bit 33 = UNDEFINED (AppleHV error)! 00:00:00.327403 NEM: Bit 34 = UNDEFINED (AppleHV error)! 00:00:00.327406 NEM: Bit 35 = UNDEFINED (AppleHV error)! 00:00:00.327409 NEM: Bit 36 = UNDEFINED (AppleHV error)! 00:00:00.327411 NEM: Bit 37 = UNDEFINED (AppleHV error)! 00:00:00.327414 NEM: Bit 38 = UNDEFINED (AppleHV error)! 00:00:00.327417 NEM: Bit 39 = UNDEFINED (AppleHV error)! 00:00:00.327420 NEM: Bit 40 = UNDEFINED (AppleHV error)! 00:00:00.327423 NEM: Bit 41 = UNDEFINED (AppleHV error)! 00:00:00.327426 NEM: Bit 42 = UNDEFINED (AppleHV error)! 00:00:00.327429 NEM: Bit 43 = UNDEFINED (AppleHV error)! 00:00:00.327432 NEM: Bit 44 = UNDEFINED (AppleHV error)! 00:00:00.327435 NEM: Bit 45 = UNDEFINED (AppleHV error)! My OS is: ProductName: macOS ProductVersion: 13.5.2 BuildVersion: 22G91 The CPU of course supports virtualization: sysctl -a | grep machdep.cpu.features machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C Virtualization is of course enabled in the machine (showvminfo): Hardware Virtualization: enabled Nested Paging: enabled Large Pages: enabled VT-x VPID: enabled VT-x Unrestricted Exec.: enabled AMD-V Virt. Vmsave/Vmload: enabled IOMMU: None Paravirt. Provider: Default Effective Paravirt. Prov.: None How can I fix/enable hardware virtualization on my Mac?

The number of performance and efficiency cores differs wildly between all the variants of the Apple silicon M cpus and Apple usually does not list these even in the technical specs. Is there a way to get the number of performance cores and efficiency cores and the CPU model from within Terminal?

I have an old MacBook Pro that I found laying about my house and it is specifically a MacBookPro9,2. I am aware that I can upgrade the RAM to 16GB DDR3 and that I can convert the hard drive to SSD; but I am wondering if there are other parts of the laptop that I can upgrade like the CPU, fan, or something of that nature if at all possible. If someone could shed some light on this, I would be grateful.

Intel mobile CPUs now have a really low base frequency and a high Turbo Boost freq, e.g. i5 2.4~4.1 GHz. Turbo at 3.8+ makes it go all the way up to 100°C. Using 'Turbo Boost Switcher' to disable TB makes the freq too low at 2.4. Is there any way to limit CPU freq at some intermediate value like 3.2?

I noticed that my MacBook gets hot and noisy (fans) when using VS Code (v1.31). The Activity Monitor shows the process **Code Helper** using more than 100% of CPU. It started happening with one repository which is huge. Only one window opened, no files opened, and it always uses more than 100% CPU. Checking in Microsoft/GitHub, there was an issue reported but they closed it saying *"This issue has been closed automatically because it needs more information and has not had recent activity."* , but it is still an ongoing issue. I tried some of the recommendations in the comments but didn't work. Does anybody has more info and/or know how to avoid this? Is it possible to make some configurations for VS Code to not burn the MacBook?

After a couple of days, when I have Safari open, I have an unexplainable high CPU load, apparently system time. launchservicesd is active with 50%-110% CPU load. The load disappears immediately when I close Safari. The load appears roughly one minute after I open Safari. I have no plugins and no particular webpage open. Just the Google search page but the load is independent of opened pages or tabs.

My 2008 iMac CPU fan runs at full speed. I tried to control the speed via Mac Fan Control app but no luck, I can control the other fans perfectly. Short context: The iMac belonged to my father, he had it in his company, I was a little young, I remember that they had to take the Mac to technical service because it was getting hot and since they repaired it and returned it to my father the fans were always going fast. Now that I am older, 2 years ago I decided to replace the GPU to bring back to life the iMac because the screen had so many lines. While I assembly the iMac I remember and noticed a connection between two solder points on the CPU fan connector. I have a suspicion that this is the reason why the CPU fan is running like this, I don't have a picture but I will leave an image recreating what I saw when I put the iMac together, it would be helpful if someone can confirm if this is the case.

One or another of the various macOS background daemons that comes with the operating system is always popping up and using a ton of CPU in the background. This is generally slightly bothersome, but it's *really* annoying while I'm trying to play demanding video games that really need the system's full attention. This visibly hurts the framerate and I need to go and investigate in iStat Menus or something to nuke the offending process manually. Is there a way to comprehensively pause or at least aggressively throttle *all* system background activity while I'm doing something demanding? Mostly I want this for applications that are demanding of input responsiveness, like video games, but it would be nice for CPU intensive batch jobs that might take an hour or two to run, too; tell the system to please chill out in the background and not suck up either CPU or I/O to let the jobs run either more repsonsively or faster. I'm being non-specific because “Why is daemon X taking up so much CPU” is a common genre of question on this site and others like it (previously , previously , previously , previously , previously , previously , previously , previously , previously , previously , previously ). *All* of these daemons are implicated at various points. Probably the worst offenders are syspolicyd, AMPDevicesAgent, and worst of all suggestd, but all the usual suspects show up at one point or another. As such, I'm not looking for a *permanent* answer for how to fix these problems all the time, i.e. how to make these daemons go away, because: 1. There's too many of them; I am resigned to just having weird energy leaks and performance problems until Apple provides some more transparency for their background daemons. 2. At least for right now, they're *mostly* behaving themselves *most* of the time, and I realize they provide value by indexing things and doing stuff in the background to provide responsiveness in the moment. 3. With an Apple Silicon machine, they appear to mostly be persistently scheduled onto the Efficiency cores and have less of a devastating performance and battery impact than they used to, as a result. What I'm looking for is more of a *temporary* fix for when I need maximum performance, which would allow me to simply quiet down the background performance interference rather than shutting it down completely. I know the system needs this stuff to run for all the functionality to work and I don't want to take an axe to necessary parts of the OS, but I'd also like to get a consistent 120 FPS in 5-year-old games without dropping to 2-3FPS for a minute and getting killed because it was *really* important to Mail.app to make sure I could instantly search for some direct marketer's phone number because it downloaded a new message into its spam folder.

I recently bought an MacBook Pro Late 2011 with an i7 2.2 GHz and 4 GB of RAM. I wanted to get started in some mobile development and learn how to work with macOS. So this was a good offer online. Until now I am happy with this product. But of course 4 GB of RAM are not much when you develop. I mainly want to work with React Native and eventually with libGDX. My question is. **Will this MacBook still be capable if I upgrade some of the components, or won't it meet the requirements of a development machine for things like mobile apps and games?**

Suddenly the *diagnosticd* daemon rise up to over 200% CPU usage, even with Xcode is not running, on OS X Mojave 10.14.1 I can't figure out it. The fans become very noisy.