3 ms·
Just as a reference point, I didn't see any measurable slowdown on mkfile (New-Item) throughput on Windows 10 after applying the patch. I suspect this may be mo
by Bitcoin_McPonzi 9y ago
Just as a reference point, I didn't see any measurable slowdown on mkfile (New-Item) throughput on Windows 10 after applying the patch. I suspect this may be more of a filesystem issue.
I also tried this:
$f = new-object System.IO.FileStream c:\temp\test.dat Create, ReadWrite
$f.SetLength(8GB)
$f.Close()
with no speed difference on a patched and unpached system
- busterarm 9y agoAs stated elsewhere, this may be because of architectural choices in MacOS that are affected by Meltdown. The file system drivers run in their own process.
- luckydude 9y agoSo I'm not a Windows expert but I've done file system work. If windows is reasonably smart it will support files with unallocated blocks. Setting the length to 8GB is not the same as writing 8GB in any reasonable file system. I'd retry with a script that actually writes the data.
- cmurf 9y agoNTFS and APFS support sparse files, HFS+ does not.