upvote

points

by pie_flavor6 hours ago |
comments
upvoteby satvikpendem4 hours ago|
next
[-]
Rust literally compiles ~4x faster on WSL than on the Windows command line, on the same hardware, so try that and see. Also set up the mold or wild linker as well as sccache, although sccache is OS agnostic so you can use it on macOS too. Make sure your code is on the WSL side not on /mnt/c which is the Windows side though, that will kill compilation speed.

https://www.reddit.com/r/rust/s/CsEy9bLivK

reply
upvoteby fluoridation3 hours ago|
parent|
next
[-]
That has not been my experience at all; I get pretty much the same times on the same machine on Linux and Windows. Something weird has happening to that person. Someone mentioned Defender, and that could certainly be it, as I have it totally disabled (forcibly, by deleting the executable).
reply
upvoteby michaelcampbell3 hours ago|
parent|
prev|
[-]
At least 10 years ago, some IBM tools I was forced to use worked faster in a linux VM on Windows (through VirtualBox) than on Windows.
reply
upvoteby rstat15 hours ago|
prev|
next
[-]
I'd wager that's more likely due to Windows than the hardware. Like sure the hardware does play a part in that but its not the whole story or even most of it.

My C++ projects have a python heavy build system attached where the main script that runs to prepare everything and kick off the build, takes significantly longer to run on Windows than Linux on the same hardware.

reply
upvoteby m_mueller5 hours ago|
parent|
[-]
Afaik a lot of it is ntfs. It’s just so slow with lots of small files. Compare unzipping moderately large source repos on windows vs. POSIX, it’s day and night.
reply
upvoteby p_ing5 hours ago|
parent|
next
[-]
No, it’s not NTFS, it’s the file system filter architecture of the NT kernel.
reply
upvoteby mattbee3 hours ago|
parent|
[-]
I had internalised that it was Windows Defender hooking every file operation and checking it against a blacklist? I've had it forced off for years.
reply
upvoteby PaulHoule5 hours ago|
parent|
prev|
[-]
Just deleting 40,000 files from the node_modules of a modest Javascript project can thoroughly hammer NTFS.
reply
upvoteby fluoridation3 hours ago|
parent|
[-]
I think part of that is Explorer, rather than NTFS. Try doing it from the console instead. rd /q /s <dir>.
reply
upvoteby PaulHoule3 hours ago|
parent|
[-]
It still takes a lot longer than Linux or Mac OS X.
reply
upvoteby fluoridation3 hours ago|
parent|
[-]
NTFS is definitely slower to modify file system structures than ext4.
reply
upvoteby PaulHoule2 hours ago|
parent|
[-]
A big part of it is that NT has to check with the security manager service every time it does a file operation.

The original WSL for instance was a very NT answer to the problem of Linux compatibility: NT already had a personality that looked like Windows 95, just make one that looks like Linux. It worked great with the exception of the slow file operations which I think was seen as a crisis over Redmond because many software developers couldn’t or wouldn’t use WSL because of the slow file operations affecting many build systems. So we got the rather ugly WSL2 which uses a real Linux filesystem so the files perform like files on Linux.

reply
upvoteby fluoridation20 minutes ago|
parent|
[-]
I don't know about ugly. Virtualization seems like a more elegant solution to the problem, as I see it. Though it also makes WSL pointless; I don't get why people use it instead of just using Hyper-V.
reply
upvoteby thewebguyd5 hours ago|
prev|
next
[-]
Try adding your working directory to the exclusions for windows defender, or creating a Dev Drive instead in settings (will create a separate partition, or VHD using ReFS and exclude it from Windows defender). Should give it a bit of a boost.
reply
upvoteby everfrustrated4 hours ago|
prev|
next
[-]
Apple buries this info but the memory bandwidth on the M series is very high. Doubly and triply so for the Pro & Max variants which are insanely high.

Not much in the PC line up comes close and certainly not at the same price point. There's some correlation here between PCs still wanting to use user-upgradable memory which can't work at the higher bandwidths vs Apple integrating it into the cpu package.

reply
upvoteby chocochunks2 hours ago|
parent|
[-]
They don't bury it. It's literally on the spec page these days. And LPCAMM2 falls somewhere between the base M and Pro CPUs while still being replaceable.

The new MacBook Neo is a less than half the memory bandwidth of the base model MacBook Air.

reply
upvoteby 0x4575 hours ago|
prev|
next
[-]
That's most likely because windows indexes and scans files rustc produces. My linux machines demolish my iMac in rust compilation.
reply
upvoteby ErneX4 hours ago|
parent|
[-]
Intel iMac?
reply
upvoteby 0x4574 hours ago|
parent|
[-]
M4. To be fair I bought it as a pretty ssh terminal in living room into compute in another room.
reply
upvoteby teaearlgraycold1 hours ago|
prev|
[-]
You’re running Windows unironically?
reply