Comment by embedding-shape
Comment by embedding-shape 4 days ago
Windows seemingly hate many tiny files, even in sharded directories, many ecosystems suffered because of this; node_modules, .git, the examples are many.
Comment by embedding-shape 4 days ago
Windows seemingly hate many tiny files, even in sharded directories, many ecosystems suffered because of this; node_modules, .git, the examples are many.
> To be fair on this default windows drive formatting is not well suited to many small files in general
How is that fairer? :P They set the defaults, they could change it, yet they don't. Seems entirely fair to point out shitty defaults as faults of their OS, regardless of how that came to be.
Yeah, I remember trying to delete a fully loaded Python installation that had found its way onto a OneDrive-managed folder. After a chat with IT, I learned that OneDrive can only delete X number of files at once. We agreed that the most practical solution was for me to spend an hour deleting files by hand, and choose another drive next time. Fortunately I don't really depend on OneDrive as a backup, since GitHub does that job well enough.
The other thing is that both Git and OneDrive are in some sense fiddling with your file system at once.
Even without OneDrive, ever tried to delete a directory with millions of small files? Even sharded, takes like 30 minutes, on fast SSDs...
> The other thing is that both Git and OneDrive are in some sense fiddling with your file system at once.
Why would .git be fiddling with your file system? It writes into .git, and changes files, but shouldn't do more than that.
To be fair on this default windows drive formatting is not well suited to many small files in general.
Unrealengine taking 40 extra gigs because of underutilization on small files is one rampant case.
Large python project disk ballooning is another.
That it's file copy move is also dramatically bad at handling such scenarios compounds this further as can be seen by shuffling the same lot with teracopy vs explorer and windows default behavior irrespective of drive formatting. Can easily be hours of difference.