Quote from: Turbor on February 27, 2012, 01:06:50 AM

There seems to be some sort of longpoll (or other connection) issue between GPUMAX and the ZTEX mining software. I get lots of rejects and overflows. BitMinter and EMC work without problem. I have no idea what the problem is. The poll loop time jumps up and also getwork and submit time. If i ping the pool the timing is about 200ms. That's not brilliant but should work ? No problems with cgminer and my 3 GPUs.

Here is what i get with BitMinter and EMC.

Code:

bus-0-0: ztex_ufm1_15d3-0001-02-05: f=208.00MHz, errorRate=0.02%, maxErrorRate
=0.74%, hashRate=208.0MH/s, submitted 18 new nonces, luckFactor=1.03
bus-0-0: ztex_ufm1_15d3-0001-02-06: f=212.00MHz, errorRate=0.99%, maxErrorRate
=1.86%, hashRate=209.9MH/s, submitted 16 new nonces, luckFactor=0.94
bus-0-0: poll loop time: 15ms (USB: 0ms network: 15ms) getwork time: 144ms su
bmit time: 293ms
Total hash rate: 417.9 MH/s
Total submitted hash rate: 409.5 MH/s
--------
bus-0-0: ztex_ufm1_15d3-0001-02-05: f=208.00MHz, errorRate=0.12%, maxErrorRate
=0.74%, hashRate=207.8MH/s, submitted 15 new nonces, luckFactor=1.03
bus-0-0: ztex_ufm1_15d3-0001-02-06: f=212.00MHz, errorRate=0.46%, maxErrorRate
=1.86%, hashRate=211.0MH/s, submitted 9 new nonces, luckFactor=0.91
bus-0-0: poll loop time: 15ms (USB: 0ms network: 15ms) getwork time: 179ms su
bmit time: 280ms
Total hash rate: 418.8 MH/s
Total submitted hash rate: 404.5 MH/s
--------
New block detected by long polling
bus-0-0: ztex_ufm1_15d3-0001-02-05: f=208.00MHz, errorRate=0.26%, maxErrorRate
=0.74%, hashRate=207.5MH/s, submitted 11 new nonces, luckFactor=1.01
bus-0-0: ztex_ufm1_15d3-0001-02-06: f=212.00MHz, errorRate=0.96%, maxErrorRate
=1.86%, hashRate=210.0MH/s, submitted 11 new nonces, luckFactor=0.91
bus-0-0: poll loop time: 16ms (USB: 0ms network: 16ms) getwork time: 187ms su
bmit time: 287ms

And now GPUMAX Undecided

Code:

bus-0-0: ztex_ufm1_15d3-0001-02-05: Using LongPolling URL http://gpumax.com:8332
/listenChannel
bus-0-0: ztex_ufm1_15d3-0001-02-05: f=200.00MHz, errorRate=0.00%, maxErrorRate
=0.00%, hashRate=200.0MH/s, submitted 1 new nonces, luckFactor=0.36
bus-0-0: ztex_ufm1_15d3-0001-02-06: f=200.00MHz, errorRate=0.00%, maxErrorRate
=0.00%, hashRate=200.0MH/s, submitted 0 new nonces, luckFactor=0.00
bus-0-0: poll loop time: 145ms (USB: 0ms network: 145ms) getwork time: 1416ms
submit time: 1078ms
Total hash rate: 400.0 MH/s
Total submitted hash rate: 71.6 MH/s
--------
Warning: jsonParse: Parameter `data' not found
bus-0-0: ztex_ufm1_15d3-0001-02-05: Set frequency to 204.00MHz
bus-0-0: ztex_ufm1_15d3-0001-02-06: Set frequency to 204.00MHz
bus-0-0: ztex_ufm1_15d3-0001-02-05: f=204.00MHz, errorRate=0.00%, maxErrorRate
=0.00%, hashRate=204.0MH/s, submitted 16 new nonces, luckFactor=1.00
bus-0-0: ztex_ufm1_15d3-0001-02-06: f=204.00MHz, errorRate=0.00%, maxErrorRate
=0.00%, hashRate=204.0MH/s, submitted 13 new nonces, luckFactor=0.77
bus-0-0: poll loop time: 475ms (USB: 0ms network: 475ms) getwork time: 1730ms
submit time: 2104ms
bus-0-0: Warning: 10 overflows occured. This is usually caused by a slow network
connection.
Total hash rate: 408.0 MH/s
Total submitted hash rate: 357.9 MH/s
--------
bus-0-0: ztex_ufm1_15d3-0001-02-05: Set frequency to 208.00MHz
bus-0-0: ztex_ufm1_15d3-0001-02-06: Set frequency to 208.00MHz
New block detected by block monitor
New block detected by long polling
bus-0-0: ztex_ufm1_15d3-0001-02-05: Set frequency to 212.00MHz
bus-0-0: ztex_ufm1_15d3-0001-02-06: Set frequency to 212.00MHz
New block detected by long polling
bus-0-0: ztex_ufm1_15d3-0001-02-05: Set frequency to 208.00MHz

It's not really a problem as much as it is people buying shares on pools that can't handle the load which we are still fine turning to protect our miners. Updates coming soon will address this and make buyers pay for rejects on pools that have issues so the miners are not penalized for it.

EDIT: We get a lot of pools ops testing their system which is not something miners should have to pay for with rejects and stales.