4 ms·
In most of the benchmarks down it outperforms NTFS. What’s going on there?
by vlovich123 5y ago
In most of the benchmarks down it outperforms NTFS. What’s going on there?
- sam0x17 5y agoIt turns out it's actually very easy to outperform off-the-shelf file systems depending on what your metric is. I discovered this when I was developing BitFort (abandoned project) which made use of WinFsp on Windows and pure FUSE on Linux. In my case the secret was having all the paths available in a fast in-memory data structure. I was dealing with a remote cloud file system, yet I was able to open up folders and browse around the file system faster than NTFS can with LOCAL file systems because every path and the MIME type is already in memory. For some applications (i.e. if you have trillions of small files) this might be a memory hog but for most I imagine it would be just fine. Seems like something OSes should have a toggleable option for...
- mikevm 5y agoBitFort sounds interesting - is the source code available? Also, what did you use to build your awesome looking resume page? https://resume.sam0x17.dev/ https://resume.sam0x17.dev/ :)
- notRobot 5y agoThat page does look pretty awesome!
- sam0x17 5y agoThank you I actually used a template that was posted on HN years ago https://github.com/Thomashighbaugh/resume https://github.com/Thomashighbaugh/resume
- sam0x17 5y agoI've been toying with the idea of releasing the bitfort source code as open source, but the usefulness is limited as it only worked with a very specific version of Node back in 2018 and the key dependencies (in particular the FUSE one) no longer works. If I were to re-write I would do it in Rust for sure.
- mikevm 5y agoI see. I was asking simply because I was interested in learning interesting things from the actual source code instead of actually running it :) If you are interested in sharing it privately, let me know and I'll email you!
- jpeloquin 5y agoAccording to the docs [0] it's in part due to an unequal comparison: "[WinFsp] outperforms NTFS in most scenarios (an unfair comparison as NTFS is a disk file system and WinFsp is tested with an in-memory file system)." I guess the point is just that WinFsp is fast enough for practical use. [0] https://github.com/billziss-gh/winfsp/blob/master/doc/WinFsp-Performance-Testing.asciidoc https://github.com/billziss-gh/winfsp/blob/master/doc/WinFsp...
- vlovich123 5y agoYeah, I assumed it was going to be an in-memory comparison but that’s super misleading and doesn’t let one get a sense of the overhead of the system itself.
- R0b0t1 5y agoAs mentioned in other comments it is an unequal comparison, but it's easy to outperform NTFS on Windows as the NTFS driver has some serious lock contention issues that make directory enumeration slow.