From: Nikolaus R. <Nik...@ra...> - 2013-02-22 01:21:54
|
David Strauss <dav...@pu...> writes: > On Mon, Feb 18, 2013 at 8:22 PM, Nikolaus Rath <Nik...@pu...> wrote: >> That doesn't make sense. The high level API is implemented on top of the >> low level API, so it cannot possibly be faster. It could be the case >> that NTFS3g isn't as clever as the FUSE library that implements the high >> level API when using the low level API, but that's something that would >> be specific to NTFS3g and probably not too hard to fix either. > > Totally possible. I didn't investigate their claim [1] further, but here it is: > > "The high level interface performs generally better because several > system calls are grouped to form a single file system call [which] can > generally be processed in the file system with a couple of inode > openings (for the requested file and parent directory), whereas at low > level more file system calls are needed causing reopenings of inodes." I'm going to be bold here and claim that this claim is total nonsense. The number of system calls for the high and low level API is the same. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C |