GT3pccb

Hello @[vincentkfu](https://github.com/vincentkfu), this explains the fallocate in windows. https://github.com/axboe/fio/issues/833 IMHO, overwrite=0 should result on no overwrites at all, otherwise we are always overwriting which entirely different than first allocations. "Note...

thank you for dicing into this. Do you have an update on what it is happening? Thanks

@sitsofe they are 2 different flags, and they are not antonyms in windows. The -file_flag_no_buffering and -file_flag_no_write_through are not mutually exclusive. Possible configurations for Buffered/write-though Buffered + write-through Unbuffered +...

Hello Sitsofe, can we make it so they are not antonyms? There are some optimization changes in the storage stack and Bitlocker for different NvME and RDIM use-cases that would...

In place writes-overwrites are as expected. iodepth_batch_submit and iodepth_batch_complete_max do not change the behavior.

Sitsofe, the queue differential is consistent across both AMD and Intel platforms, for all device types RAW/Initialized/File System.

Hi, I am root, and even adding sudo does not help. I have a question and I hope you can help. I am running into this error https://github.com/Aorimn/dislocker/issues/160 as well....

Isn't the problem with get counter is a lot slower when having to get a bunch of counters, if you do a Get-CimInstance Win32_PerfRawData_PerfDisk_LogicalDisk you get a bunch of very...

@rob-scheepens I was not suggesting to use get-counter :) ; although I am not a developer I reckon the using Get-CimInstance is way more effective. I can't find how would...

@rob-scheepens I was referring to formatted and of course I am using this to do this in a powershell script to monitor firmware latencies in hundreds of NvMEs during our...