77 karma · joined August 18, 2021
The much more standard class AB still uses 25% with no output, 100 W idle would be a stereo 200 W amplifier. Or a 5x 80 W surround amplifier.
There's a bug with the patch to enable it, tracking issues in other packages, so they seem to be in the process.
Many boycott them here in Sweden, in part due to their views on unions. And while they often have the lowest price in comparisons, they are not doing to good economically last I heard.
Enterprise Resource Planning apparently, not Erotic Role-Play.
Is this even a question? They prevent massive amounts of death.
> Portions of northern and western India, especially areas near the borders with Pakistan and Nepal, may endure the most extreme heat.
Wikipedia:
> Summer in northwestern India starts from April and ends in July, and in the rest of the country from March to May. [...] > The hottest month for the western and southern regions of the country is April; for most of North India, it is May. - https://en.m.wikipedia.org/wiki/Climate_of_India
Seems to align fairly well?
Yeah, about that.. https://mobile.twitter.com/Bitfinexed/status/150262605519403...
That's a bold claim without presenting anything really backing it up?
How so? For example I can see when the higher summer temperatures becomes an issue and reduce my timings, then tighten them again as it gets colder. No more random crashes where I wonder if it's my RAM or something else.
Currently doing 3333MT/s CL14 on 4x16GB of 2666MT/s ECC. I use CL16 in the summer. Since the memory sticks barely are affected by the heat, and that ECC errors occur on the same slot of the motherboard regardless of which stick is in there, I assume its the memory controller on the CPU in combination with four sticks of memory that's the limiting factor here.
After fiddling around a bit I decided to try the MuQSS CPU scheduler and was blown away. Not only was the scheduled backup unnoticeable, on top of that I could throw a 16 thread compilation job on my 8core/16thread CPU and I'd not notice the system being under load. I might've lost a few frames per secone when occasionally playing some FPS games, but possibly lowered throughput be damned, this was bliss.
Unfortunately it seems to not be updated anymore. So I tried the newcomers on the block, BMQ and PDS. With BMQ I would start dropping iSCSI connections since my PC wouldn't manage to reply to a ping in five seconds. PDS fit better. While MuQSS could handle a load of 40-45 before I started noticing UI-latency, PDS tops off at around 20. And when it starts to stutter, it's worse than with MuQSS, but since it's not that often that I'm at those loads I'm quite OK with the current situation.
All this with untuned schedulers, they might behave very differently with some tuning.