Topic: [ANN][POOL] ZERGPOOL.com - Multialgo, autoexchange, 0.5% fee, 250+ coins - page 11. (Read 57362 times)

This pool is stealing my coins!
Look on statistics how your mined coins just going down each time.
STAY AWAY
 

Confirmed, argon2d-dyn still has the stale share problem.

Power2b is still looking good. No rejects, starting diff is a little higher, latency has come down a bit.

argon2d-dyn

CCminer TCP API: server started on 0.0.0.0:4028
[12:06:33] INFO  - Start user session
[12:06:34] INFO  - Setting new difficulty: 64 (0.000976563)
[12:06:34] INFO  - Block height 413100 : Network difficulty 0.389216
[12:06:34] INFO  - Received new job #9e0
[12:06:35] INFO  - 1/0 Accepted : diff=0 : 90,28KH/s
[12:06:38] INFO  - 2/0 Accepted : diff=0 : 725,5KH/s
[12:06:39] INFO  - 3/0 Accepted : diff=0 : 726,5KH/s
[12:06:50] INFO  - 3/1 Rejected : diff=0, reason: Invalid job id
[12:06:58] INFO  - 3/2 Rejected : diff=0, reason: Invalid job id
[12:06:59] INFO  - 3/3 Rejected : diff=0, reason: Invalid job id
[12:07:02] INFO  - 3/4 Rejected : diff=0, reason: Invalid job id
[12:07:14] INFO  - 3/5 Rejected : diff=0, reason: Invalid job id
[12:07:16] INFO  - 3/6 Rejected : diff=0, reason: Invalid job id
[12:07:18] INFO  - 3/7 Rejected : diff=0, reason: Invalid job id
[12:07:21] INFO  - 3/8 Rejected : diff=0, reason: Invalid job id
[12:07:29] INFO  - 3/9 Rejected : diff=0, reason: Invalid job id
[12:07:31] INFO  - 3/10 Rejected : diff=0, reason: Invalid job id
[12:07:33] INFO  - 3/11 Rejected : diff=0, reason: Invalid job id

Network latency has shot up more on power2b, now rarely under 300 ms.
It appears to corespond to an increase in hash rate at the pool.

Users might help by setting a higher diff using the password field.

8 threads or more should be -p d=0.1 minimum, 16 threads should be at least 0.2
and higher still for more threads.

On the encouraging side the stale share problem has not returned, very clean mining now
and fewer stale shares than expected considering the network latency.

Things have been good for several hours, check your PM.

Edit: Network latency has increased from 150ms to 190 ms on power2b. Haven't tested
other affected algos but lyra2v3 is still 150ms.

Edit2: The increased latency may be server overload due to stratum diff too low. The starting
diff is way to low for a decent CPU and I don't see it ever increasing. An i7 submits  around
1 share per second at the starting diff for power2b. If that's the case for everyone and vardiff
isn't working then it's going to cause problems.

Speaking of diff many GPU algos have a minimum diff too high for CPU even though many can
be mined  successfully with a good CPU. Vardiff will only lower by one step. Setting the diff
manually is also limited to one step below the default starting diff.

Setting a high default is reasonable to deal with big GPU rigs but it would be nice for it to
step low enough to accomodate CPUs. Unless it's your intention to discourage CPU mining on those algos.

Is that still reoccuring? What is your full command line?

x21s - fpga

That was disappointing. After a proud announcement and promising results the problem
returned and, silence.

It's all fucking fpga to blame

Rejects are back!

Edit: stratum is also dropping, maybe ongoing work.

Looking good! rejects have completely stopped on power2b.

argon2d-dyn also looks good to me where it didn't before.

Thanks.

Argon 2dyn

[14:46:37] INFO  - Received new job #cd
[14:46:47] INFO  - 1/0 Accepted : diff=0 : 631,1KH/s
[14:46:49] INFO  - 2/0 Accepted : diff=0 : 685,0KH/s
[14:46:53] INFO  - 3/0 Accepted : diff=0 : 749,0KH/s
[14:46:59] INFO  - 3/1 Rejected : diff=0, reason: Invalid job id
[14:47:00] INFO  - 3/2 Rejected : diff=0, reason: Invalid job id
[14:47:02] INFO  - 3/3 Rejected : diff=0, reason: Invalid job id
[14:47:03] INFO  - 3/4 Rejected : diff=0, reason: Invalid job id
[14:47:08] INFO  - 3/5 Rejected : diff=0, reason: Invalid job id
[14:47:09] INFO  - 3/6 Rejected : diff=0, reason: Invalid job id
[14:47:11] INFO  - 3/7 Rejected : diff=0, reason: Invalid job id
[14:47:12] INFO  - 3/8 Rejected : diff=0, reason: Invalid job id
[14:47:15] INFO  - 3/9 Rejected : diff=0, reason: Invalid job id
[14:47:17] INFO  - 3/10 Rejected : diff=0, reason: Invalid job id
[14:47:18] INFO  - 3/11 Rejected : diff=0, reason: Invalid job id
[14:47:19] INFO  - 3/12 Rejected : diff=0, reason: Invalid job id
[14:47:19] INFO  - 3/13 Rejected : diff=0, reason: Invalid job id
[14:47:19] INFO  - 3/14 Rejected : diff=0, reason: Invalid job id

UPDATE

1. Tremendous work improving mining experience and mostly aiding "Invalid jobs" has been completed. Changes are effecting on all CPU algos, and we are rolling out to other gradually.

Yes

Yup, same problem.The problem is the pool isn't sending new jobs properly
so the miner keeps hashing the old stale job.

As I demonstrated in a previous post I collected data showing the miner received
a job that was already stale and the pool had already rejected shares submitted using it.
That's just plain wrong.

Would be nice to get it fixed.

and not only. happens on x16, neoscript, often with the password mc = "coin". I feel that one of the miners is connected to the pool with the wrong settings.

12:39:02] INFO  - 24/32 Rejected : diff=0.00606529, reason: Invalid job id
[12:39:06] INFO  - 24/33 Rejected : diff=0.0100769, reason: Invalid job id
[12:39:07] INFO  - 24/34 Rejected : diff=0.0122791, reason: Invalid job id
[12:39:07] INFO  - 24/35 Rejected : diff=0.0233635, reason: Invalid job id
[12:39:11] INFO  - 24/36 Rejected : diff=0.0117603, reason: Invalid job id
[12:39:11] INFO  - 24/37 Rejected : diff=0.00913617, reason: Invalid job id
[12:39:11] INFO  - 24/38 Rejected : diff=0.0159683, reason: Invalid job id
[12:39:11] INFO  - 24/39 Rejected : diff=0.00591861, reason: Invalid job id
[12:39:14] INFO  - 24/40 Rejected : diff=0.01579, reason: Invalid job id
[12:39:18] INFO  - 24/41 Rejected : diff=0.0143914, reason: Invalid job id
[12:39:22] INFO  - 24/42 Rejected : diff=0.0097482, reason: Invalid job id
[12:39:22] INFO  - 24/43 Rejected : diff=0.0596705, reason: Invalid job id
[12:39:22] INFO  - 24/44 Rejected : diff=0.00616638, reason: Invalid job id
[12:39:26] INFO  - 24/45 Rejected : diff=0.0130139, reason: Invalid job id
[12:39:26] INFO  - 24/46 Rejected : diff=0.00646398, reason: Invalid job id
[12:39:27] INFO  - 24/47 Rejected : diff=0.00700622, reason: Invalid job id
[12:39:28] INFO  - 24/48 Rejected : diff=0.00715171, reason: Invalid job id
[12:39:31] INFO  - 24/49 Rejected : diff=0.0338959, reason: Invalid job id
[12:39:32] INFO  - 24/50 Rejected : diff=0.0072279, reason: Invalid job id
[12:39:33] INFO  - 24/51 Rejected : diff=0.00604158, reason: Invalid job id
[12:39:37] INFO  - Setting new difficulty: 768 (0.0117188)
[12:39:37] INFO  - Block height 386980 : Network difficulty 0.666345
[12:39:37] INFO  - Received new job #9d418
[12:39:37] INFO  - 24/52 Rejected : diff=0.00732371, reason: Invalid job id
[12:39:46] INFO  - 25/52 Accepted : diff=0.0216072 : 9630KH/s
[12:39:57] INFO  - 26/52 Accepted : diff=0.0237028 : 9631KH/s
[12:40:06] INFO  - 26/53 Rejected : diff=0.014315, reason: Invalid job id
[12:40:13] INFO  - 26/54 Rejected : diff=0.015676, reason: Invalid job id
[12:40:18] INFO  - 26/55 Rejected : diff=0.0122919, reason: Invalid job id

If it's stale shares it's the same problem I reported previously and still hasn't been fixed.
It happens on the new power2b also.

Ratio 20/80% (80 - rejected) Delay of norms 50 ms. There are no such problems with Suprnova.

How many is many? What's the reject reason? Does it look anything like this problem?

https://bitcointalksearch.org/topic/m.52287385

If you get a run of stale shares it could be the problem above. A stale share occasionally is
normal. How's your network latency? You'll get more stale shares with higher latency.

very many rejected on DYN (argon2d-dyn) CryptoDredge.

x16rv2   -   also FPGA