Quote from: bible_pay on January 06, 2018, 02:35:15 PM

Quote from: pkman999 on January 06, 2018, 05:36:08 AM

Dear Rob
Can you tell me?
Why? Our mining project to get low coins?
Maybe i am error for test , the info below

1 PC = 24 core = share 48
1 PC = 24 core (tested 1 of 1vCPU = total 24 vPC ) = share 91
1 PC = 24 core (tested 1 of 4vCPU = total 6 vPC) = share 62
Same PC ~Same Ram ~Same network

Big Share= get more coin or not?

I called top of 3 big dog to tested . This is correct detail data.
Please fix the problem.

If you feel this is good at BBP future that you keep doing that.
Big pool fee is ok , I support.
But low coin of day that is not good.
Huh

I hope BBP will being just，fair and open.
I don't want any misunderstanding . Please explain. Love BBP Love this coin.

Thanks Rob ,Have are nice day

From Hong Kong ...Man

I want to find the root of the problem, if there is an inconsistency, I want us to at least quantify it.
I do not want high pool fees for the long term. I believe with auto-payment, the fees will drop back to normal within a month.

I dont think this is enough info however, to hone in on the problem.
We are going to need a whole thread, Im going to need a volunteer to be an arbiter, and I believe there is enough info out there between the miner, the code, and the wise to figure out where the bottleneck is- whether its in a nonce limit, or a wait state, or a solo-mine vs Pool.

Alex has done a lot of testing on his VMs and found he has the ability to scale his rewards appropriately, so I think its possible to break this problem down into sub problems.

First create a thread here:
http://forum.biblepay.org/index.php?board=6.0

Then if we could have a volunteer work with Pkman to break the problem down into quantifiable pieces, and ask him for more info, such as his getmininginfo start, duration, then getmininginfo stop, make columns in the sheet for that and figure out where the problem is.

This is me volunteering for the second time.

There is something very clearly wrong when my strongest processor is getting less than a third of the hash of my weakest so I have a vested interest to find out why.