Question: Completed/Failed WU's?

9 views
Skip to first unread message

[H] Nitrobass24

unread,
Jan 1, 2010, 2:53:08 PM1/1/10
to hfm-net
Harlam how are these values being calculated?

In my log file, it says that i have completed 956 WUs but in the
application it resets when i restart the client.

harlam357

unread,
Jan 2, 2010, 4:08:12 PM1/2/10
to hfm-net
That's exactly right. It's a count based on the most recent client
start, or "Client Run" (I call it). The log parser looks for the
strings FINISHED_UNIT, EARLY_UNIT_END, UNSTABLE_MACHINE, and others to
determine these counts.

There's already an Issue entered here: http://code.google.com/p/hfm-net/issues/detail?id=59

As stated in the Issue, HFM does capture the "Number of Completed
Units:" line in the FAHlog.txt file, but there is nowhere in the main
UI where it is currently reported. This total value is tracked by the
client, not HFM. Conversely, there is no "Number of Failed Units:"
count that is tracked by the client. If HFM were to persist a value
here, it would have to be persisted by HFM and not the client. I plan
to open up these options in the future, but first HFM needs to keep a
more detailed history of what has happened, not just what currently is
happening - getting to this point will take some time and planning
since the persistence of this data involves much more in terms of
future features than just reporting Completed and Failed WU counts.

The point of the current feature implementation is to see the ratio of
completed to failed units in the most recent run - this is most
helpful for GPU clients (since they tend to EUE more) - one might
change their clocks on a card and then want to see the completed to
failure rate at those clocks. Then stop the client and start up again
with a different set of clocks. I find this more helpful than knowing
how many units it has done over the life of the client.cfg file, which
is where the "Number of Completed Units:" is stored.

Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages