Windows OS: Windows 10
Hardware Information
CPU: AMD 3700x
Main Board: Gigabyte B450 Auros M
Memory: Corsair Vengeance LPX 64GB (4x16GB) 3200MHz
Hard Drives: WD30EFRX
PrimoCache Version:
Screenshot(s) of your PrimoCache's main dialog showing cache configuration and statistics:
I added three graphs which are PrimoCache version, Cache Configuration, and Defer-write Mode setting.
Problem Description:
I set the latency for defer-write as 10 seconds.
From the description, Write Mode Idle-Flush will flush the defer-write bytes when the latency is reached or the system is idle.
However, from my experiment, Primocache 4.3.0 doesn't flush defer-write bytes after latency time.
For example, if I start a download of a 1GB file, it doesn't flush the bytes even after 20 seconds.
If I switch the Write Mode to Native, I can see the hard disk starts writing after 10~11 seconds.
Is this a bug? or this is the expected behavior of the feature?
Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
- Attachments
-
- Primocache version.jpg (34.2 KiB) Viewed 4156 times
-
- Cache Confirutaion.jpg (92.06 KiB) Viewed 4156 times
-
- Advanced Defer-write.jpg (39.27 KiB) Viewed 4156 times
Last edited by arrenwu on Sat Jul 29, 2023 9:46 pm, edited 1 time in total.
Re: Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
Its not OR, its AND.
It will write your data when the system is idle, but not before the defer-write time has expired.
It will write your data when the system is idle, but not before the defer-write time has expired.
Re: Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
The description for Idle-Flush is
"In addition to the behavior of Native mode, it will also flush all deferred data to disk when Windows is idle."
It doesn't look like AND.
Besides, if you set Latency to a longer value, say 60 sec, you can see PrimoCache flushes the defer-write before Latency is reached.
"In addition to the behavior of Native mode, it will also flush all deferred data to disk when Windows is idle."
It doesn't look like AND.
Besides, if you set Latency to a longer value, say 60 sec, you can see PrimoCache flushes the defer-write before Latency is reached.
Re: Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
You are right. The logic is OR, not AND. Can you fix the error in the images you uploaded? The images cannot be displayed. Thanks.
Re: Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
Can you tell me which one you can't see?
I can see all of them from my browser (Edge).
I can see all of them from my browser (Edge).
Re: Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
I'm sorry for the late response. All images cannot be displayed. The host imgur.com initially showed that there was an error in the image, and now shows a http 409 error. Can you upload these images to the forum instead of using imgur.com? You can edit your post and then click the "Attachments" tab to upload your images and then place them in your post. Thank you.
Re: Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
I edited the article and attached three pictures.Support wrote: ↑Thu Jul 27, 2023 4:06 amI'm sorry for the late response. All images cannot be displayed. The host imgur.com initially showed that there was an error in the image, and now shows a http 409 error. Can you upload these images to the forum instead of using imgur.com? You can edit your post and then click the "Attachments" tab to upload your images and then place them in your post. Thank you.
Re: Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
Thank you. We will check this issue.
Re: Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
Is there any update on this issue?
Re: Write Mode Idle-Flush doesn't flush bytes after latency time is reached.
I'm really sorry I forgot to update the progress here. We have confirmed this issue. It will be fixed in the next version along with other fixes. Thank you.