Well, yes, that's why it throttles. The sustained power dissipation of M1 Air is around 7-10W. Once it reaches high temperatures it will reduce it's clock to bring down the power consumption to those levels Third-party reviewers observed throttling of around 20% under heavy load (
https://www.notebookcheck.net/Apple...le-M1-CPU-humbles-Intel-and-AMD.508057.0.html)
You mention that your M1 gets laggy and sluggish. That is definitely not normal behavior. I have no reason to doubt you, but lagging under load is simply not common experience with these laptops. There must be some third factor that causes this.
Curious. You don't think 20% slower is not laggy and sluggish? Maybe I'm just more sensitive to it. (if it's only 20%, it feels even slower to me)
VM's is the third factor I think. they're awfully hard on a machine, especially one that is doing some emulation inside the VM, not to mention its taking cycles away from the host. (and IO, and RAM). My Air is 16G of RAM, and that's pretty much my bare minimum. I don't know if Java apps cause more strain, but I usually have my Midrange Access/development software running. Plus I usually have Chrome and Safari open, with multiple tabs and maybe also firefox. Thunderbird email. If I'm home, the TV app is open to airplay to my TV.
Then in the VM, Domino Notes email client, Excel and Access, A VPN (IKEv2) up and running. Maybe Visual Studio, maybe not. Maybe Word.
On my Windows PC's i can have more than one VM open at a time, but I never even tried on the Air.
And then there's my want of running an emulation package like UTM to run x86 Windows when the software gets a bit better. I reached my highest temp running Windows in a UTM VM. (118F) And no, I didn't leave it running to see how fast it would lower and stabilize the temp.
Apologies if I misunderstood. But you wrote yourself "I do have an i9 desktop and it doesn't throttle. (it's got cooling that can handle it.)" and you previously wrote that you define throttling as running below the maximal clock.
I don't remember I ever said that throttling is defined by running below the maximum clock, but if I did, that was wrong. It's possible I was talking about something like intentional underclocking.. Sorry for the misunderstanding!
Running at or close to maximal clock is definitely not normal operation for any of these CPUs (although it can be done with appropriate power delivery and cooling. Mac Pro can run Xeons at full turbo — takes over 300W thought).
Agreed! Not something I would usually do these days. In my youth, I might have done some overclocking before the age of turbo, but it always caused some instability, and I hate that more than a machine feeling slower than i think it should.
Maybe it would be helpful to the discourse to define what throttling actually means. Here is how I understand throttling (and as far as I know, this is the industry-standard definition): "running below the advertised spec (base clock) under heavy sustained load"
That's fair, but I would add "because of heat" to the end of your definition. The heat based throttling is really all I'm concerned about. And precisely why I never even tried running an i9 laptop -- WAY too many people complaining about sluggish i9's in laptops.
My desktop has a couple of serious fans on it to keep it from throttling (my definition). Yes it makes a lot noise, but noise is acceptable.
In any case, I just ordered a 14" MBP M1 Pro and I'm using the Air as a trade in. The MiniLED, active cooling, more cores, was too much of a draw for me, even with the notch, which I will use that new app to black the menu bar out and probably run more apps full screen. <g>