From 646818a65c50b6aab08e620f56385e8643c4a2f4 Mon Sep 17 00:00:00 2001 From: Bill Zissimopoulos Date: Mon, 6 Jun 2022 15:44:45 +0100 Subject: [PATCH] doc: WinFsp Performance Testing Update with new tests and analysis for 2022. --- doc/WinFsp-Performance-Testing.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/WinFsp-Performance-Testing.asciidoc b/doc/WinFsp-Performance-Testing.asciidoc index b05ffba4..bc424572 100644 --- a/doc/WinFsp-Performance-Testing.asciidoc +++ b/doc/WinFsp-Performance-Testing.asciidoc @@ -32,7 +32,7 @@ For the NTFS file system we use the default configuration as it ships with Windo Note that the sequential nature of the tests represents a worst case scenario for WinFsp. The reason is that a single file system operation may require a roundtrip to the user mode file system and such a roundtrip requires two process context switches (i.e. address space and thread switches): one context switch to carry the file system request to the user mode file system and one context switch to carry the response back to the originating process. WinFsp performs better when multiple processes issue file system operations concurrently, because multiple requests are queued in its internal queues and multiple requests can be handled in a single context switch. -For more information refer to the link:doc/analysis.ipynb[Performance Testing Analysis] notebook. This notebook together with the `run-all-perf-tests.bat` script can be used for replication and independent verification of the results presented in this document. +For more information refer to the link:WinFsp-Performance-Testing/analysis.ipynb[Performance Testing Analysis] notebook. This notebook together with the `run-all-perf-tests.bat` script can be used for replication and independent verification of the results presented in this document. The test environment for the results presented in this document is as follows: ---- @@ -152,7 +152,7 @@ image::WinFsp-Performance-Testing/rdwr_nc_write_page_test.png[] ==== mmap_read_test -This test measures the performance of memory mapped reads. NTFS and WinFsp have identical performance here, which actually makes sense because memory mapped I/O is effectively always cached and most of the actual I/O is done asynchronously by the system. +This test measures the performance of memory mapped reads. NTFS and WinFsp have identical performance here, which actually makes sense because memory mapped I/O is effectively cached by buffers that are mapped into the address space of the process doing the I/O. image::WinFsp-Performance-Testing/mmap_read_test.png[]