Suggestion: performance data for Writes
Suggestion: performance data for Writes
At the bottom of the Performance Statistics screen, next to the Read Hit Rate, could we have a Writes Prevented statistic? (Write bytes deferred / Write Bytes) * 100 for percentage.
Re: Suggestion: performance data for Writes
Thanks. I think this is easy to add it.
Re: Suggestion: performance data for Writes
added in FC 0.6.1
Re: Suggestion: performance data for Writes
Thank you... I did notice one thing...
One of the big selling points in Fancycache -VS- the 'other' cache software is that only FancyCache recognized TRIM, using it to reduce the writes to the SSD for cached data as well as saving on other writes.
I think it might be better to either:
Have the writes deferred (Write bytes deferred / writebytes) * 100 and just below that Write bytes Prevented 100-((Write bytes deferred / writebytes) * 100)
OR
change Write Bytes deferred to write bytes prevented only : 100-((Write bytes deferred / writebytes) * 100)
With the first method, we get the best of both worlds. You have such a unique cache program that we need the stats to brag about it.
One of the big selling points in Fancycache -VS- the 'other' cache software is that only FancyCache recognized TRIM, using it to reduce the writes to the SSD for cached data as well as saving on other writes.
I think it might be better to either:
Have the writes deferred (Write bytes deferred / writebytes) * 100 and just below that Write bytes Prevented 100-((Write bytes deferred / writebytes) * 100)
OR
change Write Bytes deferred to write bytes prevented only : 100-((Write bytes deferred / writebytes) * 100)
With the first method, we get the best of both worlds. You have such a unique cache program that we need the stats to brag about it.
Re: Suggestion: performance data for Writes
Thanks.
well, we know users want to view the percentage that is prevented. However currently we are not able to get the exact value for this statistics item.
The formula "100 - (write bytes deferred / total write bytes) * 100" doesn't exactly refer to the Write bytes Prevented because there are "Deferring Blocks (Current)" waiting for write. In consideration of performance, the value of "Deferring Blocks" is counted in blocks instead of bytes. So we don't know the exact bytes prevented. Besides, "write bytes deferred" is not updated if the Defer-Write is in pausing state.
well, we know users want to view the percentage that is prevented. However currently we are not able to get the exact value for this statistics item.
The formula "100 - (write bytes deferred / total write bytes) * 100" doesn't exactly refer to the Write bytes Prevented because there are "Deferring Blocks (Current)" waiting for write. In consideration of performance, the value of "Deferring Blocks" is counted in blocks instead of bytes. So we don't know the exact bytes prevented. Besides, "write bytes deferred" is not updated if the Defer-Write is in pausing state.
Re: Suggestion: performance data for Writes
Yeah, I guess it would be kinda hard... Unless the value is only updated when the cache is flushed... But still the issue with a paused cache...
Hmmm... Actually, even if the write cache is paused, the writes prevented percentage would be accurate on flush since there are writes happening outside the cache which would reduce the percentage.
Hmmm... Actually, even if the write cache is paused, the writes prevented percentage would be accurate on flush since there are writes happening outside the cache which would reduce the percentage.
Re: Suggestion: performance data for Writes
thanks. Have studied the possiblity. But according to the current program design, there are still some difficulties to be overcome.magic-man wrote:Unless the value is only updated when the cache is flushed