3 ms·

This seems to be a known phenomenon - https://stackoverflow.com/questions/197162/ntfs-performance-and-large-volumes-of-files-and-directories https://stackoverfl

by g_p 6y ago

This seems to be a known phenomenon - https://stackoverflow.com/questions/197162/ntfs-performance-and-large-volumes-of-files-and-directories https://stackoverflow.com/questions/197162/ntfs-performance-... That's looking at large numbers of files and folders, but we all know that overheads like these tend to come about due to inefficiency at the per-file level scaling up. Also might be worth checking you've got 8.3 filenames disabled and stripped from existing files (https://docs.microsoft.com/en-gb/archive/blogs/josebda/windows-server-2012-file-server-tip-disable-8-3-naming-and-strip-those-short-names-too https://docs.microsoft.com/en-gb/archive/blogs/josebda/windo...). Although in general I must admit I find Linux offers better performance due to less "hidden cruft" running - perhaps the issue is background services like Windows defender (and all the other ones that don't immediately leap out) like you suggest.

pacoverdi 6y ago
Thanks, I hadn't heard about 8.3 filenames and it turns out they are activated on my laptop (somewhat recent Dell Latitude 5491). However, unlike the article you linked, I only have a C: drive and Windows won't let me change that setting easily. Will investigate further... EDIT: finally managed to do it by tweaking a register. Weird, my filesystem already contains a mix of files with and without 8dot3names. Will monitor this in the future to see if there is an impact on FS performance.
- g_p 6y ago
  I hadn't either, and I'm keen to see if it makes any difference on a local PC (as opposite to a large file server with huge numbers of files stored). It strikes me Microsoft struggles with significant legacy across much of their product range, that is holding them back. Between filesystems still supporting 8.3 naming, and client links to AD seemingly assuming that clients are on trusted LAN networks (in 2021), I wonder if their backwards compatibility could be their downfall. In a competitive market where they weren't quite so dominant, it would be interesting to see if a startup could get good enough API compatibility through WINE that they could offer a commercial "windows replacement" distribution, offering remote management via an AD-compatible interface (that can run zero-trust via SSL, the way it should be designed in 2021).
- pacoverdi 6y ago
  In case someone reads this (6 days later). Looks like git rebase is a lot faster now \o/

by g_p 6y ago

pacoverdi 6y ago

Thanks, I hadn't heard about 8.3 filenames and it turns out they are activated on my laptop (somewhat recent Dell Latitude 5491). However, unlike the article you linked, I only have a C: drive and Windows won't let me change that setting easily. Will investigate further... EDIT: finally managed to do it by tweaking a register. Weird, my filesystem already contains a mix of files with and without 8dot3names. Will monitor this in the future to see if there is an impact on FS performance.

g_p 6y ago
I hadn't either, and I'm keen to see if it makes any difference on a local PC (as opposite to a large file server with huge numbers of files stored). It strikes me Microsoft struggles with significant legacy across much of their product range, that is holding them back. Between filesystems still supporting 8.3 naming, and client links to AD seemingly assuming that clients are on trusted LAN networks (in 2021), I wonder if their backwards compatibility could be their downfall. In a competitive market where they weren't quite so dominant, it would be interesting to see if a startup could get good enough API compatibility through WINE that they could offer a commercial "windows replacement" distribution, offering remote management via an AD-compatible interface (that can run zero-trust via SSL, the way it should be designed in 2021).
pacoverdi 6y ago
In case someone reads this (6 days later). Looks like git rebase is a lot faster now \o/