Even logging is disabled, the change of the refresh interval still logging.
This is a low priority bug.
----
I just trying to reduce the hard disk usage on the netbook, after I disabled the logging, clean up the log.
I changed the refresh interval (governor), and found that it is logged into the log.
Anyways, this is a low priority bug.
---------Off-topic
Just a question, when governor (with a 100ms refresh interval) is restraining the software, the CPU usage increased to 5% CPU usage, it is on a Atom CPU.
So did this is normal, as it is a Atom CPU?
Anyways, if it is not restraining, the CPU usage is normal, like <0.01%. ;)
Thanks.. Yea, that log event is so infrequently issued, if ever, that I missed this. I'll be sure to fix it!
Yup, roger.
And also someone has asking for a setting to enable delay writing(buffer then write) the log, to prevent performance hit for I/O. :)
It already does that, and uses low priority I/O to write to the log. It also marks the file as 'temporary', which causes the OS to cache writes to it in RAM before committing to disk much longer than a regular file.
The refresh rate log entry when log is off is fixed. Build 6.7.0.43+
Ok, thank for that info and the fix. ;)