10 ms·
Why is Windows so slow?
- markokocic 15y agoI'm not sure if it is related, but the fact is that file system operation on windows are much slower that on Linux. I remembering that copying large ISO image from one windows partition to another windows partition using Total Commander under Wine on Linux was faster that doing it directly on Windows. I also remember that I was able to create file copy utility in assembly as a homework assignment that was couple times faster than windows/dos copy command. The only two reasons I can think of that explain this are: 1 - noone cares about windows fileystem performance. 2 - someone decided that it shouldn't be too fast.
- m_for_monkey 15y agoIn Total Commander you can configure the buffer sizes used while copying. Maybe in your homework you chose the right buffer size too (and, of course, asm is fast, but hard to write, I'm sure you didn't bother too much with error checking and other "small" problems). Moreover, the optimal buffer size is different for small and large files, maybe Windows is not optimized for large size like a DVD image.
- markokocic 15y agoAs for Total commander example, that was out of the box experience, without any tweaks. I just wanted to point out that even when using emulation layer to access Windows native filesystem type, Linux was significantly faster on file system operations. As for my homework "copy" command, I know that it is not fully replacement to file copy windows command, but if copy operations takes >10min, all those checks and additional tasks shouldn't make IO bound operation take couple time longer than what some student implemented as homework.
- etfb 15y agoSomeone posted the question on StackOverflow and it got closed as "not constructive". Is there a way to browse the "not constructive" questions on SO? They seem to be all the best ones.
- Mithrandir 15y agoRef: http://stackoverflow.com/questions/6916011/how-do-i-get-windows-to-go-as-fast-as-linux-for-compiling-c http://stackoverflow.com/questions/6916011/how-do-i-get-wind... (By the author) Top Answer: Unless a hardcore windows systems hacker comes along, you're not going to get more than partisan comments (which I won't do) and speculation (which is what I'm going to try). 1. File system - You should try the same operations (including the dir) on the same filesystem. I came across this which benchmarks a few filesystems for various parameters. 2. Caching. I one tried to run a compilation on Linux on a ramdisk and found that it was slower than running it on disk thanks to the way the kernel takes care of caching. This is a solid selling point for Linux and might be the reason why the performance is so different. 3. Bad dependency specifications on windows. Maybe the chromium dependency specifications for Windows are not as correct as for Linux. This might result in unnecessary compilations when you make a small change. You might be able to validate this using the same compiler toolchain on Windows.
- buster 15y agoWhy should he run the ls command on ntfs rather then a native file system? In all it was a "windows vs linux" test and not a fileystem test. Testing the same filesystem wouldn't make sense here
- jharsman 15y agoPresumably to find out whether the difference lies with the filesystem or somewhere else? If Linux is still much faster, even with the same filesystem, you have eliminated one variable.
- buster 15y agoDoing some profiling and system/kernel level analysis would be much saner, imo. What's the sense in measuring how some non-native filesystem behaves? In the end you'll be benchmarking how good is fuse-ntfs vs. in-kernel-ext4 and figuring it's slower... I say, profile some code and see how much time is spent in filesystem calls.
- johnx123-up 15y agoFWIW, try disabling your AV
- qdog 15y agoThis. And anything else you can find that registers with the kernel for file system calls. Logging mechanisms, etc. Anything the kernel has to talk to about file i/o is going to slow it down.
- einhverfr 15y agoI have found Windows a bit slower but never to the extent the author suggests. But then I have generally tested on clean systems without antivirus. So I suspect that this is a huge factor, esp. because it intercepts all FS calls and checks them. That's really not what you want when compiling code.
- ervvynlwwe 15y agoThe author doesn't mention whether he is using cygwin git, or msys git. msys is faster. But even with msys, UAC virtualization is a common cause of slowness with git: http://stackoverflow.com/questions/2835775/msysgit-bash-is-horrendously-slow-in-windows-7 http://stackoverflow.com/questions/2835775/msysgit-bash-is-h... More details here: http://code.google.com/p/msysgit/issues/detail?id=320 http://code.google.com/p/msysgit/issues/detail?id=320
- obtu 15y agoSure, Cygwin does a bit of extra wrapping. The official site and just about anybody link to msysgit, however.
- false 15y agoGit under cygwin is so painfully slow, and gets exponentially slower as number of tracked files grow. Even SSD can't fully smooth out the difference :(
- evmar 15y agoI don't know this poster, but I am pretty familiar with the problem he's encountering, as I am the person most responsible for the Chrome build for Linux. I (and others) have put a lot of effort into making the Linux Chrome build fast. Some examples are multiple new implementations of the build system ( http://neugierig.org/software/chromium/notes/2011/02/ninja.html http://neugierig.org/software/chromium/notes/2011/02/ninja.h... ), experimentation with the gold linker (e.g. measuring and adjusting the still off-by-default thread flags https://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/281527606915bb36/ https://groups.google.com/a/chromium.org/group/chromium-dev/... ) as well as digging into bugs in it, and other underdocumented things like 'thin' ar archives. But it's also true that people who are more of Windows wizards than I am a Linux apprentice have worked on Chrome's Windows build. If you asked me the original question, I'd say the underlying problem is that on Windows all you have is what Microsoft gives you and you can't typically do better than that. For example, migrating the Chrome build off of Visual Studio would be a large undertaking, large enough that it's rarely considered. (Another way of phrasing this is it's the IDE problem: you get all of the IDE or you get nothing.) When addressing the poor Windows performance people first bought SSDs, something that never even occurred to me ("your system has enough RAM that the kernel cache of the file system should be in memory anyway!"). But for whatever reason on the Linux side some Googlers saw it fit to rewrite the Linux linker to make it twice as fast (this effort predated Chrome), and all Linux developers now get to benefit from that. Perhaps the difference is that when people write awesome tools for Windows or Mac they try to sell them rather than give them away. Including new versions of Visual Studio, for that matter. I know that Chrome (and Firefox) use older versions of the Visual Studio suite (for technical reasons I don't quite understand, though I know people on the Chrome side have talked with Microsoft about the problems we've had with newer versions), and perhaps newer versions are better in some of these metrics. But with all of that said, as best as I can tell Windows really is just really slow for file system operations, which especially kills file-system-heavy operations like recursive directory listings and git, even when you turn off all the AV crap. I don't know why; every time I look deeply into Windows I get more afraid ( http://neugierig.org/software/chromium/notes/2011/08/windows-hookers.html http://neugierig.org/software/chromium/notes/2011/08/windows... ).
- vog 15y ago
- iradik 15y agoHmm.. I've had an opposite experience on an atom netbook. Tried Windows Vista and Ubuntu on a netbook. The Windows netbook worked great while Ubuntu regularly would crash. Ubuntu on the netbook was unusable. Now probably I did something wrong? But just installed the latest version with default settings. Anyway I returned the netbook.
- alextingle 15y agoWere you running compiles on it??
- iradik 15y agoNo I was running a web browser and a chat program.
- reledi 15y agoThe author has an issue with speed, not stability.
- niyazpk 15y agoHere is a link from the comments: NTFS Performance Hacks - http://oreilly.com/pub/a/windows/2005/02/08/NTFS_Hacks.html http://oreilly.com/pub/a/windows/2005/02/08/NTFS_Hacks.html
- yread 15y agoNot sure about the other things, but this The default cluster size on NTFS volumes is 4K, which is fine if your files are typically small and generally remain the same size. But if your files are generally much larger or tend to grow over time as applications modify them, try increasing the cluster size on your drives to 16K or even 32K to compensate. That will reduce the amount of space you are wasting on your drives and will allow files to open slightly faster. is wrong. When you increase cluster size you will definitely not "reduce the amount of space you are wasting". 100B file will still occupy the whole 16KB ( so you will waste 15.9KB on it instead of 3.9KB with 4KB clusters. Also I would be very careful with taking advice like that from an article which is 6 years old (before introduction of Win7 or XP SP3!)
- biot 15y agoHow is a 100 byte file a valid refutation of what you quoted? It quite clearly states that you should leave the cluster size alone if your files are typically small.
- yread 15y agowell, OK let's take a guess at median filesize 4KB [1]. Then the 4KB cluster wastes some space only for half of the files whereas 16 KB wastes space for bigger proportion plus they waste additional 12KB for 50% of the files. On the other hand the paper also shows how ridiculous it is to talk about the wasted space - look at figure 14, files smaller than 16KB occupy ~1% of all space. Even if we waste space 4:1 it's still ridiculously small amount of space [1] http://www.usenix.org/events/fast11/tech/full_papers/Meyer.pdf http://www.usenix.org/events/fast11/tech/full_papers/Meyer.p...
- 15y ago
- deleted 15y ago[deleted]
- jstclair 15y agoWow, so if you want to test file system speeds, you do it by listing files - I know this just an example, but perhaps it has something to do with the speed of the terminal? There are a plethora of disk benchmarking tools - I doubt that they consistently show 40x differences. Hooves -> horses, and all that.
- vacri 15y agoThere is indeed marked differences between unix terminals - xterm is blazingly fast. Do the same test the author did with xterm and with another terminal and you'll see significant differences. cmd may just be a slow terminal masking actual windows speed.
- vacri 15y agoI will never, ever understand the downmodding on this site. There is no particular opinion in this statement - it's an informative statement that the speed of your terminal can matter. I find it strange that on a site claiming to be for hackers that a fairly opinion-free comment on terminal speed differences gets downmodded. It's hard to keep a thick skin about having your voice diminished when even your informative, unopinionated stuff gets shut down.
- shabble 15y agoMaybe I'm misunderstanding (or he's since changed his post), but: dir /s > c:\list.txt is piping it into a file. Where does the speed of the terminal affect that (in any significant fashion)? I know what you're getting at - tar --verbose can slow things down for me by sometimes a factor of 2 (for huge tarballs), but I don't think it's an issue in this situation.
- jstclair 15y agoYes, I saw the redirection. But "dir" is an built-in command in the Windows shell; is the speed of that command a benchmark-able number? Is the point to compare the speed of "ls" vs "dir", or the underlying OS/file-systems (i.e., posix vs. win32 /Ext3 vs. NTFS)? If someone tells me that "dir" is slow, I'd agree -- but that -- in itself -- doesn't imply that the filesystem is slow.
- hristov 15y agoInterestingly enough Joel Spolsky mentioned something related to the directory listing problem more than 10 years ago. See: http://www.joelonsoftware.com/articles/fog0000000319.html http://www.joelonsoftware.com/articles/fog0000000319.html In Joel's opinion it is an algorithm problem. He thinks that there is an O(n^2) algorithm in there somewhere causing trouble. And since one does not notice the O(n^2) unless there are hundreds of files in a directory it has not been fixed. I believe that is probably the problem with Windows in general. Perhaps there are a lot of bad algorithms hidden in the enormous and incredibly complex Windows code base and they are not getting fixed because Microsoft has not devoted resources to fixing them. Linux on the other hand benefits from the "many eyes" phenomenon of open source and when anyone smart enough notices slowness in Linux they can simply look in the code and find and remove any obviously slow algorithms. I am not sure all open source software benefits from this but if any open source software does, it must certainly be Linux as it is one of the most widely used and discussed pieces of OS software. Now this is total guesswork on my part but it seems the most logical conclusion. And by the way, I am dual booting Windows and Linux and keep noticing all kinds weird slowness in Windows. Windows keeps writing to disk all the time even though my 6 GB of RAM should be sufficient, while in Linux I barely hear the sound of the hard drive.
- prewett 15y agoAlong the same line, I've never understood Windows' propensity to swap out the kernel. I might have tons of free memory and half my kernel is swapped out. In fact, I've never figured out how to get it not swapped out, no matter how much memory I put in.
- jstclair 15y agoYou could try this (from an elevated command-prompt), but the general consensus is that it has a small (if any) effect: reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" -v DisablePagingExecutive -d 0x0 -t REG_DWORD -f Disable it with: reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" -v DisablePagingExecutive -d 0x1 -t REG_DWORD -f More discussion here: http://serverfault.com/questions/12150/does-the-disablepagingexecutive-registry-change-have-any-actual-effect http://serverfault.com/questions/12150/does-the-disablepagin... The easiest way (if you have enough memory) is just disable the paging file.
- barrkel 15y agoProbably a big reason for him seeing slowdowns in incremental builds with MSVC is because of link-time code generation. What seems to be link time is actually code generation time, and it's delayed because intra-procedural optimizations can be run. This kills off a lot of the benefit of incremental building - you're basically only saving parsing and type analysis - and redoing a lot of code generation work for every modification. NTFS also fragments very badly when free space is fragmented. If you don't liberally use SetFilePointer / SetEndOfFile, it's very common to see large files created incrementally to have thousands, or tens of thousands, of fragments. Lookup (rather than listing) on massive directories can be fairly good though - btrees are used behind the scenes - presuming that the backing storage is not fragmented, again not a trivial assumption without continuously running a semi-decent defragmenter, like Diskeeper.
- tankenmate 15y agoThe problem as I understand it is that Windows's file metadata cache is broken. I remember reading many years ago a posting by Linus about this but I can't find it at the moment. According to this document (http://i-web.i.u-tokyo.ac.jp/edu/training/ss/lecture/new-documents/Lectures/15-CacheManager/CacheManager.ppt http://i-web.i.u-tokyo.ac.jp/edu/training/ss/lecture/new-doc...) it would appear that directory entries have one extra level of indirection and share space with the page cache and hence can be pathologically evicted if you read in a large number of files; compiling/reading lots of files for example. On Linux however the directory entry cache is a separate entity and is less likely to be evicted under readahead memory pressure. Also it should be noted is that Linus has spent a largish amount of effort to make sure that the directory entry cache is fast. Linux's inode cache has similar resistance to page cache memory pressure. Obviously if you have real memory pressure from user pages then things will slow down considerably. I suspect that if Windows implemented a similar system with file meta data cache that was separate from the rest of the page cache it would similarly speed up. Edit: I should note, this probably wouldn't affect linking as much as it would affect git performance; git is heavily reliant on a speedy and reliable directory entry cache.
- prewett 15y agoI suspect it has something to do with NTFS updating access times by default. So every time you do anything with a file, it gets its access time updated (not modification time, access time). I don't have windows to test on, but you could try the suggestions [1][2] below. [1] http://msdn.microsoft.com/en-us/library/ms940846(v=winembedded.5).aspx http://msdn.microsoft.com/en-us/library/ms940846(v=winembedd... [2] http://oreilly.com/pub/a/windows/2005/02/08/NTFS_Hacks.html http://oreilly.com/pub/a/windows/2005/02/08/NTFS_Hacks.html (#8)
- darklajid 15y agoAs posted elsewhere and as someone pointed out in the very comments of the article: That doesn't seem to be the case for Windows 7 anymore.
- shintoist 15y agoBut most Linux distros do this by default as well. You have to mount with noatime to get rid of it.
- kinetik 15y agoLinux has defaulted to relatime since 2009.
- wazoox 15y agoIn fact nowadays most (all?) linux filesystems use relatime as default, which carries most of the advantages of both atime and noatime. See http://kerneltrap.org/node/14148 http://kerneltrap.org/node/14148 I don't know if something similar exists under windows (I suppose it doesn't).
- lloeki 15y agoMac OS X does appear to mount with atime but I happened to use this: $ cat /Library/LaunchDaemons/com.nullvision.noatime.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.nullvision.noatime</string> <key>ProgramArguments</key> <array> <string>mount</string> <string>-vuwo</string> <string>noatime</string> <string>/</string> </array> <key>RunAtLoad</key> <true/> </dict> </plist> I don't know if there's anything like relatime.
- tintin 15y agoMaybe this has something to do with the file indexer? 2 years ago I heard a lot of XP users complain that Windows was suddenly getting very slow. After some digging around I noticed that they turned on the file indexer by default after an update. Since then I always turn it of (properties of your disk) and shut down the service (Indexing Service).
- shin_lao 15y agoNTFS is a slower file system, that's probably the main reason why. Also console I/O is much better on Linux than Windows. Our software builds everyday on FreeBSD, Linux and Windows on servers that are identical. The windows build takes 14 minutes. The FreeBSD and Linux build take 10 minutes (they run at almost identical speed). Check out is more than twice slower on Windows (we use git). Debug build time is comparable 5 minutes for Windows, 4 minutes 35 on Linux. Release build time is almost 7 minutes on Windows and half that on Linux. VS compiles more slowly than gcc but overall it's a better compiler. It handles static variables better and is not super demanding about typenames like gcc is. Also gcc is extremely demanding in terms of memory. gcc is a 64-bit executable, Visual Studio is still a 32-bit execuable. We hope Microsoft will fix that in Visual Studio 2011. Its easier to parallelize gmake than Visual Studio, which also explains the better Linux build time. Visual Studio has got some weird "double level" mulithreading which is eventually less efficient than just running the make steps in parallel as you go through your make file. However our tests run at comparable speed on Linux and Windows and the Windows builds the archive ten times faster than Linux.
- vmmenon 15y ago"Why is Windows so slow? I’m a fan of Windows, specifically Windows 7." ????
- blinkingled 15y ago1) Windows FS operations are slower than Linux in general but when you add 'Realtime' Antivirus on top it gets worse. 2) Linux forks significantly faster than anything else I know. For something like Chromium the compiler is forked bazillion times and so is the linker and nmake and so on so forth. 3) Linux, the kernel, is heavily optimized for building stuff as that's what the kernel developers do day in and day out - there are threads on LKML that I can't be bothered to dig out right now but lot of effort goes in to optimizing for kernel build workload - may be that helps. 3) Linker - stock one is slower and did not do the more costly optimizations until now so it might be faster because of doing lesser than the MS linker that does incremental linking, WPO and what not. Gold is even faster and I may be wrong but I don't think it does what the MS linker does either. 4) Layers - Don't know if Cygwin tools are involved but they add their own slowness.
- nikcub 15y agoThis is a comparison of file systems, not operating systems.
- jcromartie 15y agoDon't forget forking. To benchmark the maximum shell script performance (in terms of calls to other tools per second), try this micro-benchmark: while true; do date; done | uniq -c Unix shells under Windows (with cygwin, etc.) run about 25 times slower than OS X.
- Mavrik 15y agoWell, Unix shells under Windows don't even implement forking, so this test is kinda meaningless isn't it? It's like racing cars where one of the cars has its wheels taken off.
- koenigdavidmj 15y agoCygwin has fork. The problem is that Cygwin's fork has to copy the entire address space into the new process, whereas Linux uses copy-on-write to make forking much faster (you only need to copy the page tables).
- brudgers 15y agoOverall, the author's argument is somewhat dependent on a premise that Windows 7 should be optimized for edge cases such as compiling code written for multiplatform implementation (e.g. Chrome) rather than using the managed code model around which Microsoft's development of Windows has been centered for many years. If one were optimizing Windows performance, none of the specific areas used as examples would receive much attention given user demographics. What percentage of Windows users use the command line, much less compile C programs, never mind using "cmd" shells to do so? Windows command line gurus will be using Powershell these days, not the legacy encumbered "cmd" - elsewise they are not gurus.
- WayneDB 15y agoI run Windows 7 in Boot Camp every day and it easily outperforms OS X on the same exact hardware for most common tasks (browsing files, the web, starting up apps, etc). The Windows desktop GUI system is more stable than anything else out there (meaning that it's not going to change drastically AND that it's a solid piece of software that just works) and it's as flexible as I need it to be, so that's why I stick with Windows. With virtual machines, WinSCP, Cygwin and other similar utilities, I have all the access to *nix that I need.
- r00fus 15y ago> The Windows desktop GUI system is more stable than anything else out there (meaning that it's not going to change drastically AND that it's a solid piece of software that just works) So you assume that Windows8 metro-mode won't really catch on? Also comparing OSX to Windows over the past 10 years, it's Windows that has changed more drastically, so both future and past evidence to the contrary...
- WayneDB 15y agoHow has Windows changed more drastically than OS X since 2001? To me drastic means that something very basic has changed and/or compatibility has been lost. (Things like resizable windows, full screen apps, broken finder plugin compatibility, changes to expose, addition of mission control, etc.) I don't assume, know or care to know anything about Windows Metro. It's not replacing the desktop system that I use.
- idspispopd 15y agoseparate point: while photoshop isn't on linux, there are plenty of replacements for that unless he's doing print work, which I don't think is the case, as photoshop isn't the beginning and end for print. (actually, TBH, photoshop is pretty shit for pixel work.) Also maya is available for linux, autodesk just doesn't offer a free trial like they do with windows/mac os. (Including the 2012 edition.) With no offence intended to the 3dsmax crew, as it has it's merits, but a sufficiently competent maya user won't find much use for 3dsmax.
- chris_gogreen 15y agoHard drive swap file usage, my windows machines always have a huge swap file going, my Linux and OS X machines almost never do.
- portman 15y agoI'm disappointed HN! There is a lot of pontificating, but not much science here. It takes all of 2 minutes to try this experiment yourself (plus ~8 minutes for the download). 1. Download chromium http://chromium-browser-source.commondatastorage.googleapis.com/chromium_tarball.html http://chromium-browser-source.commondatastorage.googleapis.... 2. Unzip to a directory 3. Create this batch file in the src directory, I called mine "test.bat" echo start: %time% >> timing.txt dir /s > list.txt echo end: %time% >> timing 4. Run test.bat from a command prompt, twice. Paste your output in this thread. Here is mine: start: 12:00:41.30 end: 12:00:41.94 start: 12:00:50.66 end: 12:00:51.31 First pass: 640ms; Second pass: 650ms I can't replicate the OP's claim of 40000ms directory seek, even though I have WORSE hardware. Would be interested in other people's results. Like I said, it only takes 2 minutes.
- coverband 15y agoUnfortunate that this comment doesn't get enough attention in this thread... A single person's experience will always be subjective (even with the provided technical detail). If it's not consistently repeatable, it can only be used as an anectode.
- ajross 15y agoI'm not sure what your point is. The post you're replying to is no less anecdotal. Obviously there are complicated performance interactions afoot here. In the OP's opinion (and mine) Windows is littered with these kinds of booby traps. Things usually work fast ... until they don't, and you have to dig hard to figure out why. For the most part, Linux just doesn't do that. Obviously there are performance bugs, but they get discussed and squashed pretty quickly, and the process is transparent. On the occasions I'm really having trouble, I can generally just google to find a discussion on the kernel list about the problem. On windows, we're all just stuck in this opaque cloud of odd behavior.
- barrkel 15y agoIf something is slow with respect to the OS, you can often break out procmon and examine the stacks of the poorly performing requests; or if something is stalled, you can do the same with procexp. With dbghelp configured correctly, you get symbol resolution in the OS libraries, so you can see what's going on. Worst comes to worst, you can step through the disassembly with a debugger, but it's not often required. When I have problems with Linux, I tend to have to fall back to strace or an equivalent, and I find it harder to figure out what's going on. On Solaris, if I can find the right incantations to use with dtrace, I can see where the problems are, but it's easy to get information overload. My point is, how opaque your perspective is depends on your familiarity with the system. I have less trouble diagnosing holdups on Windows than I do on other systems. That's because I've been doing it for a long time.
- peterwwillis 15y agoI'm pretty sure the "dir" takes longer than "ls" because "dir /s c:\list.txt" sorts the entire c:\ drive before looking for "list.txt". "ls -R c:\list.txt" first checks if "list.txt" exists, and fails if it doesn't. Just take out the "list.txt" and run both commands again.
- frooxie 15y agoWhat I can't wrap my head around is the amazingly slow file search (I'm using Vista). Searching for a filename I know exists in a small directory (say, 100 files) often leads to Windows searching for several minutes and then NOT FINDING THE FILE. How can that happen when Windows is able to list the contents of the directory (including the file I'm looking for) instantly?
- Lagged2Death 15y agoI am also frustrated by the indexed searching in Windows. This should have been a brilliant signature feature, and it's just execrable. If you look at the indexing options in the Vista control panel and click the "Advanced" button, you'll find a dialog box with a "File Types" tab. This horrible dialog may show you (it did for me) that some file types (i.e., filename extensions) are deliberately excluded from indexing. For some reason. You know, because you may not want to find certain things when you look for them. I guess. You'll also find the world's worst interface for specifying what kinds of file should be indexed by content. But never mind. If searching by filename and/or path is all you're after, check out Everything: http://www.voidtools.com/ http://www.voidtools.com/ If you're not using Windows as an Administrator, (and you shouldn't be) Everything won't seem very polished. But it is terrifyingly fast, and it's baffling that Microsoft's built-in search is this bad if something like Everything is possible.
- malkia 15y agoA possible faster way to read directories with one (okay, few at most kernel calls) is to use GetFileInformationByHandleEx. Here is some example: https://gist.github.com/1487388 https://gist.github.com/1487388