Usage Monitor IO from just one Drive

[rthrns]

Hello I am a newbie to skin creation. I am making a skin to report disk space usage and Read/Write activity. from what I understand I should be using the Usage Monitor plugin to do this. In the documentation it says that IOREAD and IOWRITE return b/s from all disks is it possible to set it to read only one disk? I have attached the full .ini file. Open to constructive criticism about any of the code. Thank you for your time

Code: Select all

[MeasureReadDiskC]
Alias=IOREAD
Measure=Plugin
Plugin=UsageMonitor

[MeasureWriteDiskC]
Alias=IOREAD
Measure=Plugin
Plugin=UsageMonitor

[MeterReadDiskC]
AntiAlias=1
Meter=Histogram
MeasureName=MeasureReadDiskC
MeasureName2=MeasureWriteDiskC
UpdateDivider=0
W=210
H=60
X=8
Y=0r

[mak_kawa]

For C drive, something like this;

Code: Select all

[MeasureReadDiskC]
Measure=Plugin
Plugin=UsageMonitor
Category=LogicalDisk
Counter=Disk Read Bytes/sec
Name=C:

[MeasureWriteDiskC]
Measure=Plugin
Plugin=UsageMonitor
Category=LogicalDisk
Counter=Disk Write Bytes/sec
Name=C:

Alias=IOREAD, IOWRITE is for monitoring access per process.

[rthrns]

Okay thanks a lot. Helps when I don't misunderstand the Docs

[balala]

Besides mak_kawa's reply, note one more: Update=250 in the [Rainmeter] section means four updates per second (one update per 250 milliseconds). DefaultUpdateDivider=240 in the same [Rainmeter] section means that every measure or meter which has no other UpdateDivider set, is updated once per 250 x 240 = 60,000 milliseconds = 60 seconds = 1 minute. Are you sure? This is a too long update period.
I'd probably use DefaultUpdateDivider=4, to get the measures and meters updated once per second, or even better, I'd completely renounce to DefaultUpdateDivider and would set the Update to the default value Update=1000. At least if there isn't something I skipped.

[Mor3bane]

Besides mak_kawa's reply, note one more: Update=250 in the [Rainmeter] section means four updates per second (one update per 250 milliseconds). DefaultUpdateDivider=240 in the same [Rainmeter] section means that every measure or meter which has no other UpdateDivider set, is updated once per 250 x 240 = 60,000 milliseconds = 60 seconds = 1 minute. Are you sure? This is a too long update period.
I'd probably use DefaultUpdateDivider=4, to get the measures and meters updated once per second, or even better, I'd completely renounce to DefaultUpdateDivider and would set the Update to the default value Update=1000. At least if there isn't something I skipped.

for clocks and timers that are based on a time measure, i set the whole skin to update=990 the timer will not timeout due to sys checks or other skins refreshing causing a slight delay and the skin missing potentially an entire 1000 ms - there would still be a rate of attrition but if the bogging down did occur randomly in relation to processor lag it would not be frequently enough to actually rate as a delay.