WinDev VS VoltageShift

Trying to research this a little more, I came across a post that certainly seems to mimic the issue.

> compressed memory

doesn't solve much and it's been available in all other OS for a long time.

many reported that compressed memory can negatively impact performances in certain scenarios

For example

https://github.com/microsoft/Windows-Dev-Performance/issues/...

You can see pretty easily if you ever try to delete a node_modules folder on Windows: https://github.com/microsoft/Windows-Dev-Performance/issues/17 There's some anectdotal evidence in there that FS performance is better in Linux even when Linux is emulated in WSL2 instead of native Windows.

issue on github

Addressed an issue where when explorer.exe is launched from an elevated process was using a lower memory priority, impacting the performance of all processes launched after it (Issue #55).

A bug has been filed about this on the WinDev repo, might help resolve it faster if it gets some upvotes: https://github.com/microsoft/Windows-Dev-Performance/issues/...

There are performance issues with POSIX-first software on Windows. There is an open issue for the Windows team about it on Github. You can read more about it here. That's why WSL is needed.

I own a 2015 MacBook Pro 13", and do not plan on purchasing a new MacBook soon. I recently searched for how to improve battery life, and accidentally stumbled upon undervolting when I forgot to add "mac" at the end of my search. My curiosity was piqued, and I looked into it more. It turns out that there is one tool for undervolting a Mac, called voltageshift. It can be found on Github here, and is written by siscreative, abn5x, ridvan-cln, Artoria2e5, and Charlyo.

After downloading it here, extract the .zip and then navigate to the folder in terminal.

Additionally, I did undervolt CPU & GPU to reduce the heat a bit and save some battery with VoltageShift (it’s still not good though, I get like 4 hours of SoT total.)

Begin by following the existing undervolt guide https://github.com/sicreative/VoltageShift and extract the bios and search for two values: CFG Lock and Overclocking Lock

Setup This needs you to install VoltageShift (find on GitHub) to your System with your preferred settings, create two Shortcuts and Save.

Yeah, I gotcha what you're trying to do though the official method for the said action was using the VoltageShift (https://github.com/sicreative/VoltageShift). So with it you'd build a launch daemon to start things up with the appropriate parameters. But just brainstorming upon your particular set of issues, I think you should maybe look into rebuilding your PM settings in the exact same way you generate the pmset upon building up the new machine. Which means deleting the two pmset files and letting macOS generate the new ones upon the restart, which, in whole honesty, might be the culprit seeing how the CPU has changed in the meantime and it could be the culprit. Obviously this is just an in-theory post but nevertheless something I'd look into.

This solution, just like in Windows, is unfortunately not permanent and will have to be applied on boot, and every time you wake the computer from sleep or hibernation. We will be using the latest release of VoltageShift, an Open-source software that allows us to modify MSR and undervolt. Do note that this only works on Haswell machines and newer. There's a chance you could use CPUTune or other software that is able to write to MSR values directly, but this guide exclusively focuses on VoltageShift.

As u/xartic1 mentioned, you can use volta or if you don't want to pay, you can use the library used by volta underneath - https://github.com/sicreative/VoltageShift