 ckolivas
|
5cf4e188fd
Increase pool watch interval to 30 seconds.
|
14 years ago |
|
ckolivas
|
85008a7853
Reap curls that are unused for over a minute.
|
14 years ago |
|
Con Kolivas
|
ec3d057016
Use the ringbuffer of curls from the same pool for submit as well as getwork threads.
|
14 years ago |
|
Con Kolivas
|
7d288eac9f
Implement a scaleable networking framework designed to cope with any sized network requirements, yet minimise the number of connections being reoped.
|
14 years ago |
|
Con Kolivas
|
89053c78da
There is no need for the submit and getwork curls to be tied to the pool struct.
|
14 years ago |
|
ckolivas
|
adda6e6680
Do not recruit extra connection threads if there have been connection errors to the pool in question.
|
14 years ago |
|
ckolivas
|
7638511290
We should not retry submitting shares indefinitely or we may end up with a huge backlog during network outages, so discard stale shares if we failed to submit them and they've become stale in the interim.
|
14 years ago |
|
Con Kolivas
|
b015348df4
Shorten stale share messages slightly.
|
14 years ago |
|
Con Kolivas
|
7233890d85
Protect the freeing of current_hash under mutex_lock to prevent racing on it when set_curblock is hit concurrently.
|
14 years ago |
|
Con Kolivas
|
53c22551f7
Change default behaviour to submitting stale, removing the --submit-stale option and adding a --no-submit-stale option.
|
14 years ago |
|
Con Kolivas
|
f9123f0587
Make sure to start the getwork and submit threads when a pool is added on the fly.
|
14 years ago |
|
Con Kolivas
|
5ad942d187
Faster hardware can easily outstrip the speed we can get work and submit shares when using only one connection per pool.
|
14 years ago |
|
Con Kolivas
|
628ac19977
Get rid of confusing "waiting on fresh work" part of longpoll message to minimise log width and add pool number to longpoll work restart message.
|
14 years ago |
|
Con Kolivas
|
972860c0af
Remove unused variable.
|
14 years ago |
|
Con Kolivas
|
3362a2a447
Give a longpoll message for any longpoll that detects a block change, primary or backup, and also display which pool it was.
|
14 years ago |
|
Con Kolivas
|
e1cf5029d4
Decrease utility display to one decimal place.
|
14 years ago |
|
Con Kolivas
|
7b370bb2e7
Small cosmetic output alignment.
|
14 years ago |
|
Con Kolivas
|
669b0deda3
Add pool number to stale share message.
|
14 years ago |
|
Con Kolivas
|
03fab3f438
Remove thread id display from rejected shares as well.
|
14 years ago |
|
Con Kolivas
|
86e94edb89
Set have_longpoll to true when there is at least one pool with longpoll.
|
14 years ago |
|
Con Kolivas
|
0365878ac5
Don't display the thread ID since it adds no useful information over the device number.
|
14 years ago |
|
Con Kolivas
|
08c721080d
Don't display the first 8 bytes of a share since they will always be zero at >= 1 difficulty.
|
14 years ago |
|
Con Kolivas
|
501e35a0e6
work->longpoll is reset across test_work_current so we need to recheck what pool it belongs to.
|
14 years ago |
|
Con Kolivas
|
03abb70467
Use longpolls from backup pools with failover-only enabled just to check for block changes, but don't use them as work.
|
14 years ago |
|
Con Kolivas
|
1ab318d0f3
Start longpoll only after we have tried to extract the longpoll URL.
|
14 years ago |
|
Con Kolivas
|
b1c273e71b
Check for submitold flag on resubmit of shares, and give different message for stale shares on retry.
|
14 years ago |
|
Con Kolivas
|
5ece966f07
Check for submitold before submitstale.
|
14 years ago |
|
Con Kolivas
|
ed718b2b50
Don't force fresh curl connections on anything but longpoll threads.
|
14 years ago |
|
Con Kolivas
|
eda382990a
Create one longpoll thread per pool, using backup pools for those pools that don't have longpoll.
|
14 years ago |
|
Con Kolivas
|
e502fde52b
Remove the ability to disable longpoll. It is not a useful feature and will conflict with planned changes to longpoll code.
|
14 years ago |
