CALLING OUT TO SANDOR I must say CPUminer is MUCH MUCHHHHHHHHH better looking then it was before, before you touched it, it was just one big pile of >>>>>>>>>>>>> v;slfigjs;flgjdsb;jsdn;adfjg;adghs'dfigjd'fgicmg
You did an AWESOME job buddy at least your miner is much more stable than CGminer, I actually thought i worked out the problem with cgminer but sadly I didn't, it just crashes for no reason EVEN when you have enough power and a good powered usb hub, simply put it .. .. cgminer is wrecked!! and no one wants to fix it.... Im glad someone has made something else stable and made it look similar to cgminer...
There is 1 issue with CPUminer and it is the local hashrate accuracy... ONLY local side.
One thing about Cgminer is that it is pretty accurate with the local hasrates all the way back from the GPU Tweaking and tuning days, Now in regards to your CPU miner it is showing REALLY weird local hashrates, From 76KH all the way to 900KH , ALl my miners are VMod3 @ 1200mhs they all should show 510KH locally and poolside... CPUminer seems to get more stable as time goes by but still not locally accurate. For Eg; Now the Hashrate ranges from 99KH to 590KH and its been like this for awhile .
Interestingly it seems Poolside is more accurate than local side lol.
This is very strange as it should be the other way around hehe! Anyway I SHould be getting a total hashrate of Around 20Mhz locally and poolside should be fluctuating from 19-21MH but will average out to 20mhz.... At the moment the poolside is correct and fine, but with CPUminer I am only showing 15-16-17-18 Locally At the moment, and after 15 minutes it seems to have stabilised at around 17Mhz seems like it takes awhile to warm up which shouldn't be the case in regards to these Gridseeds It should only take 5 minutes to locally warm up offcourse poolside will take longer.
I think I know the problem, I will explain below>>
VVV , By the way the reason I don't believe the total hashrate should be fluctuating that much locally is because the Gridseeds are actually pretty stable and they should reach to a max point and stay there, Have you seen how Cgminer acts? These Seeds will reach to a point of KH and stay there, they do not thermal throttle or anything, infact they are much more steady than GPUs ..
ok
so,,,,
The problem is this
>>> The way you have CPUminer calculating the Local hashrate is by how many shares are accepted, this is something the pool does and will never be accurate, Cgminer does not do this, CGMINER has the WU Column and this shows the work Load for each miner and yes this will display according to how many shares are accepted, but in -regards to local hashrate this is different and should not be calculated in this way. Maybe you can pull this certain function out of Cgminer and place it in cpuminer? @ 1200mhs These Miners should show 510.2KH-510.6KH If you do this this will mean CPUminer is now KING and no one will ever need to look anywhere else for true local hashrate.
This is the only issue I can see here , I don't care about the WU:// Cgminer also shows this but I dont know how it works there so it doesn't really matter
1 LAst thing?
MANNNN Your CPUminer is 10000000000000 times more stable.. AWESOME work!!! AWESOME!!!!!!!! and you do not have to plug each Gridseed
PS: I also PMed you
EDIT: I did some calculations and I realised I should be getting more out of these gridseeds, how can I tell if hashrate is locally correct? CGminer without a doubt showed 510KH, now I am thinking if this was correct or not? CPUminer does not show this, cpuminer shows rates based on Accepted, so seems to be matching the pool, the thing is if @ 1200mhz the grids get 510KH shouldnt this be the same for 99% of all gridseeds with the 49.9k Vmod3? Or maybe I am not giving them long enough, I am giving them 45min and then judging them, Should I be giving them atleast 10-24 hrs of continous mining before checking the hashrate?