hi dan i get this line
;"Thread HashMasher-3 could not immediately reserve a core, it may experience decayed performance.
Thread HashMasher-4 could not immediately reserve a core, as there are no more cores to assign to. If performance is degraded, attempt with fewer hashers."
when i start the miner my cpu is intel core i5 3320m it's meant to be 4 cores.
is this message an issue or shall i ignore it.
cheers
Safe to ignore. Try using fewer threads (edit config.cfg and find the only number near the end -- reduce it by one) and retest to see how it impacts your H/s -- some people get a little bit more if they use fewer hashers, varies from computer to computer.
Hi,
can you please explain what the numbers means ?
streams=hashers/cores?
H/run = ??
Streams Runs H/run Cur H/s Cur TiC% Cur WL% Argon % Sha % Shares Finds Reject
16 54 1 9.10 85.35 0.000 99.991 0.002 1 0 0
16 54 1 9.10 85.35 0.000 99.991 0.002 1 0 0
I have two identical systems, same hardware, same O/S and I have different hashrate. Im trying to figure out why...
Streams = # of threads active
Runs = kind of, how many "kernels" are run on each thread during last reporting period
H/run = how many hashes are done in each Kernel.
Cur H/s = The instantaneous hashes per second based on the executed kernels
Cur TiC% = an estimate based on wall clock vs. recorded times in the threads, how much CPU time the threads are getting. It is not super accurate, anything over 80% is usually good
Cur WL% = an estimate of "wait loss" or how long new kernels are sitting around waiting for old kernels to complete. Ignore it; just a kind of statistic for advanced tuning.
Argon % = within the kernels, how much time is spent computing Argon2i hashes, in %. Over time should trend towards > 99.99%
Sha % = within the kernels, how much time is spent computing the 5-rounds SHA-512, in %. Will be very small.
Shares = raw # of nonces found, including rejected
Finds = raw # of blocks found, including rejected (todo: I will exclude rejected)
Reject = raw # of nonces that failed to confirm, due to "bad timing" -- block update during submit -- network problem, or any other rejection (perhaps you OC'd too hard and math errors...)
Hope that helps!