read the second line of your user stats (the one in the brackets)
pps is always a problematic measure, at first i would say that a factor of 4 is really good (compared to the original client), i dont know if this is what you should expect, it’s a while ago i tested the original client the last time (maybe other users can help?). on the other hand, people like jh00 & co. (tandyuk,rbe…) are using a different measure. e.g. their PPS measure is counting every iteration of the mining process (giving them 20k “PPS”) even when the iteration hasn’t found a primechain, while my miner only counts iterations finding at least a primechain of length 1 (giving me only 3k “PPS”).
unfortunately people only see 20k PPS vs 3k PPS and going crazy about it…
I have a general question about using the miner. On all my machines I’m using -genproclimit=4, however, most of my machines only have 2 cores. Is there a downside to using more workers than you have cores? There was a message in the announce thread that seemed to indicate you should set this option to match your core count, but I figured it was worth a post just to ask…
In my (limited) experience, I am getting optimal performance by using as many threads as number of cores OR as many as hyperthreading allows, if the CPU has HT… I don’t think you can gain anything by using more than the number of cores. It will cause the processes to get cycled CPU-time. Theoretically, HT should also be less efficient due to some cycling, but on my stats it shows slightly better performance going by HT core-count than true core-count.
Newbie here: I’m using the Xolo miner (x64). Working fine on my test laptop (~2.2k primes/sec). Should I be trying to make jhprimeminer work? Are there any profit calculators?
@happific+djmien+lumierre+iheartcryptocoin+defragger:
yes, backend was stuck again >:( BUT i was able to restart everything without losing the shares of the affected hours
blocks & payout pages are available
i disabled the web sharelog/sharehistory information as this is using the same database as the share submission/payouts (and i dont want them to be affected)
i guess i have to split / duplicate all stored shares: one for the pool, one for the backend
@d2rhino:
the primes/ses measure is not really comparable between xolominer & jhprimeminer
jhprimeminer is currently not usable on beeeeer anyway, this will probably change in the future
WOW ~10 xpm a day. Care to share how fast/how many machines you are running on?[/quote]
I have 144 cores in total (xeon X5660 + i7) but need to spend some cpu ticks for the other little tasks, OS debian linux amd64.
@oleg:
you’re in the wrong forum!
this is the peercoin (ppc) / primecoin (xpm) forum
everything is alright on my side, i can connect, and the server’s looking good, please check your connection/setup or write in the pts forum
@porzione+bearmeat+Xaero:
welcome to the forum
the sharelog/history is disabled currently on the webserver, due to some major performance issues related with the database and i dont wanted to damage the productive system
they will be back, when i have a smart solution for this issue
the share reward is currently fluctuating due do the increasing amount of miners and the long confirmation time of mined blocks (2.5 days) resulting in a piled up sharelog
please get your head around CPPSRB to understand the payout system