We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Hello there,
my name is Markus and this is my first post in here.
I´m happy that this tool is available and I try to gain the best out of it. Thankyou Glenn.
My question is regarding the attached screenshot, there its displaying the different measures in using LOGICALDRIVES.
I use this code:
LOGICALDRIVES=text:,interval:15,diskio:1,chart:bar2 scale:linear max:100 series1:7 threshold:80 color1:b55393 color2:%orange% color3:%red%,threshold1:11 10000000 0000f0,threshold2:13 10000000,threshold3:7 90 0070f0, 0060f0,display:%1: %6[5.1g]/%5[3.0b]B %chart% r%15 w%16
My focus now is on
%15 average seconds per read operation
%16 average seconds per write operation
I understand this is displaying seconds, how could I show milliseconds or microseconds?
E.g. so that I can read "1,2ms" instead of "0,0012s" ?
best regards
MArkus
try this:
avg read: {{1.1f:%15*1000}}ms, write: {{1.1f:%16*1000}}ms
Thankyou Sir,
I just tested this code line:
LOGICALDRIVES=text:,interval:15,diskio:1,chart:bar2 scale:linear max:100 series1:7 threshold:80 color1:b55393 color2:%orange% color3:%red%,threshold1:11 10000000 0000f0,threshold2:13 10000000,threshold3:7 90 0070f0, 0060f0,display:%1: %6[5.1g]/%5[3.0b]B %chart% r{{%15+10}} w{{1.1f:%16*1000}}
and get as result>> r[error] w[error]
it looks that calculating is not possible for this values, most of the return variables of LOGICALDRIVES produce that [error] in combination with a calculation.
I´m using DTI version 2.11.0
best regards
Markus
I just copied your entry into 2.11.0 here and this is the result. Not sure why it's failing for you. Check the log.
Glenn,
Using this code:
LOGICALDRIVES=text:,interval:15,diskio:1,chart:bar2 scale:linear max:100 series1:7 threshold:80 color1:b55393 color2:%orange% color3:%red%,threshold1:11 10000000 0000f0,threshold2:13 10000000,threshold3:7 90 0070f0, 0060f0,display:%1: %6[5.1g]/%5[3.0b]B %chart% r{{%15+10}} w{{1.1f:%16*1000}}
LOGICALDRIVES=text:,interval:15,diskio:1,display:%1: %6[5.1g]/%5[3.0b]B r{{%15+10}} w{{1.1f:%16*1000}}
log is showing:
09-07-21 09:26:29:050 ERROR EvaluateUserFunction: [error]
Its the language. My PC is set to German formatting of numbers and dates, when switching to US its working because of the changed dot (.) and comma (,) in the variables
yep, that'll do it! the expression parser has a hard coded decimal separator, it should be referring to the locale. That will be fixed in the upcoming v3 some time in the next week.
Thanks for the bug report.
