WinFsp – FUSE for Windows – faster Than Dokany
You say in your bench that Dokan support does not support memory mapped files but it does as I can see with fsx (memory mapped read&#x2F;write enabled) running on their CI <a href="https:&#x2F;&#x2F;ci.appveyor.com&#x2F;project&#x2F;Maxhy&#x2F;dokany&#x2F;build&#x2F;1.0.1-48&#x2F;job&#x2F;axakvm0u2tqqgf6a#L1086" rel="nofollow">https:&#x2F;&#x2F;ci.appveyor.com&#x2F;project&#x2F;Maxhy&#x2F;dokany&#x2F;build&#x2F;1.0.1-48&#x2F;...</a>
It is your implementation that doesn&#x27;t support it.<p>You add lock (that will slow down the result) on Dokan implementation only <a href="https:&#x2F;&#x2F;github.com&#x2F;billziss-gh&#x2F;memfs-dokany&#x2F;commit&#x2F;03ebaebb1d5f53823fa23709cc9e710ff4f0e540" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;billziss-gh&#x2F;memfs-dokany&#x2F;commit&#x2F;03ebaebb1...</a>
After that you see that dokan is faster to list files (<a href="https:&#x2F;&#x2F;github.com&#x2F;billziss-gh&#x2F;winfsp&#x2F;commit&#x2F;595a77bd2e45347809ed46ab419a1a0df8e11b2e#diff-499e702a5a0648c27ee9e9e622f71521R109" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;billziss-gh&#x2F;winfsp&#x2F;commit&#x2F;595a77bd2e45347...</a>) You improve YOUR MEMFS winfsp implementation <a href="https:&#x2F;&#x2F;github.com&#x2F;billziss-gh&#x2F;winfsp&#x2F;commit&#x2F;f7ca9f05221040a5a88df33d8d58b87b21c1e863" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;billziss-gh&#x2F;winfsp&#x2F;commit&#x2F;f7ca9f05221040a...</a> but not on dokan ?<p>You also improve memory allocation on winfsp memfs implementation and again not on dokan <a href="https:&#x2F;&#x2F;github.com&#x2F;billziss-gh&#x2F;winfsp&#x2F;commit&#x2F;d12234bb01b3620b4fc201b9a197ef48cbefe359" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;billziss-gh&#x2F;winfsp&#x2F;commit&#x2F;d12234bb01b3620...</a><p>And last point...running it on VirtualBox O_o ? Even running it 5x time and take the best time. You cannot be sure that virtualbox has not corrupt your test. For me a benchmark on a VM is not reliable at any point.<p>My point is even if Winfsp is fast on your test with an unfair FS, I am pretty sure there is not difference with real applications on a non-virtual machine.