I apologize in advance if any of this sounds ignorant, but I'm a bit new at mining.
With the latest bfgminer build (3.9.0) pointed to the ibipot pool, I'm running a single BFL 30GHs w/ an 8 core cpu (win7 64bit). I'm getting an avg of about 12GHs on the BFL and only 4 cores are being used at ~30% at the high end (while crunching). I checked bfgminer.exe's affinity and it's set to all 8 cores. Also, bfgminer is reporting a lot of errors (further decreasing efficiency) at optimal temps (see below):
--------------------------------------------------------------------------------
BFL 0: 56.0C | 13.62/13.97/12.49Gh/s | A:116 R:16+0( 11%) HW:22/.21%
--------------------------------------------------------------------------------
Though the idea behind this coin is fantastic and I'm not giving up on it (yet), it appears that 50% of the hashing power that our lower-end miners have is being wasted.
Is there any way to tweak anything on my end to bring the hash rate up?
Note:
I also have a 1.5GH/s Antminer which is displaying all the same issues (hw errors, 50% lower hash rate, barely touches my cpu's potential, and both miner & pool reporting 0.4MH/s = 50% potential).
The HW errors do not occur when mining other coins, but does occur whether I'm solo mining or pool mining MED, so I'm wondering if it's the build of the miner...
One last note about the ibipot pool - the reported GH/s rate (on the dashboard) fluctuates dramatically and appears to be almost arbitrary. Their reported hash-rate varies anywhere from 0.8GH/s to 36GH/s while the bfgminer & CPUs on my end stays steady at ~12GH/s & 30% (respectively). Is this a known hash-rate calculation bug at the pool?
Thanks in advance for any help...
I run 3x antminer U1 using Mac and regular (bitcoin) latest bfgminer, that is pointed to latest bfgminer-med modification. It acts as proxy and does the nessesary other calculations eg:
on Mac: bfgminer (bitcoin version) -o <proxyip>:1234 -u user.2 -p 123
on win: bfgminer (med version) --http-port 1234 -o ibipot.com:3333 -u user.2 -p 123
hash is normal, hw is low.
you could try that or use startum-mining + mcproxy3 + cgminer, that appears to perform a little better, but there is a bottelneck as stratum-mining can only utilize 1 CPU core at the moment. I know there is a new and better solution under development.
regarding to pool hashrate, this is calculated on submitting valid shares.. if miner window show one hashrate that includes sharer which are not valid, then pool only calculates valid shares. now the hash on pool is calculated using last 10min valid sharerate, usually sharerate is on average correct, but it will start jumping when miner submits invalid shares. I will look onto it when I have more time for that. At the moment I think it is not that important, as there is some more thing for me to do on pool
EDIT:
Mac screen:
Windows bfgminer (med) proxy screen
