Using Proxmox 7.2 with Windows 10 guest.
I noticed that compiling a codebase with about 12000 small files (215 MB total) takes a very long time. Same with for example Subversion-Commit which goes through all files and checks for changes.
After some experimenting, I coded a small program that goes through all files and just reads them. The first pass takes 67 seconds. Second pass takes 0.7 seconds (since the files are cached, probably in windows).
It's a Ryzen 4750, with a 2TB Samsung 980pro NVME.
I don't have a barebone windows machine to test this out directly, but I remember this was usually quite fast, a few seconds.
So there is probably a bottleneck somewhere... any idea what I could reconfigure to try to get these file reads up to speed?
For now I will be using this "Directory Warmer" program to keep reading the files every few minutes and keep it all cached. But I'd like to know if there's a more proper solution.
(I know that there's some performance overhead, but this seems too slow to be normal)
I noticed that compiling a codebase with about 12000 small files (215 MB total) takes a very long time. Same with for example Subversion-Commit which goes through all files and checks for changes.
After some experimenting, I coded a small program that goes through all files and just reads them. The first pass takes 67 seconds. Second pass takes 0.7 seconds (since the files are cached, probably in windows).
It's a Ryzen 4750, with a 2TB Samsung 980pro NVME.
I don't have a barebone windows machine to test this out directly, but I remember this was usually quite fast, a few seconds.
So there is probably a bottleneck somewhere... any idea what I could reconfigure to try to get these file reads up to speed?
For now I will be using this "Directory Warmer" program to keep reading the files every few minutes and keep it all cached. But I'd like to know if there's a more proper solution.
(I know that there's some performance overhead, but this seems too slow to be normal)