Con Kolivas
|
57a73dce34
|
Test for sequential getwork failures on a pool that might actually be up but failing to deliver work as we may end up hammering it repeatedly by mistake.
|
12 years ago |
Kano
|
a6bf276f6b
|
API - Add last share difficulty for devices and pool
|
12 years ago |
Kano
|
89b6989fb3
|
Store and report Accepted,Rejected,Stale difficulty in the summary and API
|
12 years ago |
Kano
|
7ede5a59bd
|
WorkTime - display prevblock for scrypt
|
12 years ago |
Kano
|
923b9e0d86
|
Calculate work difficulty for each getwork and display with WorkTime debug
|
12 years ago |
Kano
|
796f3906c1
|
WorkTime - multiple nonce per work and identify the work source
|
12 years ago |
Kano
|
bd3c98aaaf
|
Optional WorkTime details with each Accepted/Rejected work item
|
12 years ago |
Kano
|
99f0607fb2
|
API add display of and setting queue,scantime,expiry
|
12 years ago |
Kano
|
e649aa3906
|
HW: dont submit bad shares
|
12 years ago |
Kano
|
fced503ed6
|
save individual pool proxy settings to config
|
12 years ago |
Kano
|
0ac350547e
|
--default-config - allow command line to define the default configuration file for loading and saving
|
12 years ago |
Kano
|
cef9731fbc
|
CURL support for individual proxy per pool and all proxy types
|
12 years ago |
Kano
|
307d8da034
|
HW: error counter auto for all devices - ztex code not fixed
|
12 years ago |
Kano
|
4023872b76
|
count device diff1 shares
|
12 years ago |
Kano
|
568b0fed89
|
API allow full debug settings control
|
12 years ago |
Con Kolivas
|
57c3b12f64
|
Sort the blocks database in reverse order, allowing us to remove the first block without iterating over them. Output the block number to debug.
|
12 years ago |
Con Kolivas
|
f97bf2e2ac
|
Keep the local block number in the blocks structs stored and sort them by number to guarantee we delete the oldest when ageing the block struct entries.
|
12 years ago |
Con Kolivas
|
b768758818
|
Test for lagging once more in queue_request to enable work to leak to backup pools.
|
12 years ago |
Con Kolivas
|
579c1299c6
|
There is no need to try to switch pools in select_pool since the current pool is actually not affected by the choice of pool to get work from.
|
12 years ago |
Con Kolivas
|
4a210d4eff
|
Only clear the pool lagging flag if we're staging work faster than we're using it.
|
12 years ago |
Con Kolivas
|
d1683f75c9
|
needed flag is currently always false in queue_request. Remove it for now.
|
12 years ago |
Con Kolivas
|
1b7db5bc9c
|
thr is always NULL going into queue_request now.
|
12 years ago |
Con Kolivas
|
0e0093e602
|
Select pool regardless of whether we're lagging or not, and don't queue another request in switch pool to avoid infinite recursion.
|
12 years ago |
Con Kolivas
|
7992e5f3c8
|
Carry the needed bool over the work command queue.
|
12 years ago |
Con Kolivas
|
37fa7d36d4
|
Move the decision to queue further work upstream before threads are spawned based on fine grained per-pool stats and increment the queued count immediately.
|
12 years ago |
Con Kolivas
|
618b3e8b11
|
Track queued and staged per pool once again for future use.
|
12 years ago |
Con Kolivas
|
4ca288e820
|
Limit queued_getworks to double the expected queued maximum rather than factoring in number of pools.
|
12 years ago |
Con Kolivas
|
ad90269508
|
Minimise the number of getwork threads we generate.
|
12 years ago |
Con Kolivas
|
0feb679b67
|
Only keep the last 6 blocks in the uthash database to keep memory usage constant. Storing more is unhelpful anyway.
|
12 years ago |
Con Kolivas
|
b74b54d95b
|
Check we haven't staged work while waiting for a curl entry before proceeding.
|
12 years ago |
Con Kolivas
|
61df3013a8
|
Ignore the submit_fail flag when deciding whether to recruit more curls or not since we have upper bounds on how many curls can be recruited, this test is redundant and can lead to problems.
|
12 years ago |
ckolivas
|
edd9b81622
|
Do not add time to dynamic opencl calculations over a getwork.
|
12 years ago |
Con Kolivas
|
9de3a264fc
|
Increase max curls to number of mining threads + queue * 2, accounting for up and downstream comms.
|
12 years ago |
Con Kolivas
|
3ab5dba67e
|
Queue enough requests to get started.
|
12 years ago |
Con Kolivas
|
3ebe8e8c77
|
Revert "Scale maximum number of curls up according to work submission rate."
This reverts commit 1dff48e759 .
Did not increase staged work even though it decreased queues.
|
12 years ago |
Con Kolivas
|
3ceb57b8f6
|
There is no point trying to clone_work in get_work() any more since we clone on every get_work_thread where possible.
|
12 years ago |
Con Kolivas
|
787e40a7cc
|
There is no point subtracting 1 from maxq in get_work_thread.
|
12 years ago |
Con Kolivas
|
1dff48e759
|
Scale maximum number of curls up according to work submission rate.
|
12 years ago |
Con Kolivas
|
56be75228e
|
Roll back to 45f0ac7b48
|
12 years ago |
Con Kolivas
|
c1886c9c99
|
Assume we need a full allotment of work after lp and make clone_work clone_lpwork only.
|
12 years ago |
Con Kolivas
|
82fa6e25d5
|
There is no point running through clone_work from get_work() now that cloning is done from the get_work_thread.
|
12 years ago |
Con Kolivas
|
caa266ca3b
|
Make opt_queue a function of mining threads in clone_work as well.
|
12 years ago |
Con Kolivas
|
652efc6939
|
opt_queue should be a function of the number of mining threads.
|
12 years ago |
Con Kolivas
|
8ed381f78a
|
Only set lagging flag once there are no staged work items.
|
12 years ago |
Con Kolivas
|
f5ac84b804
|
select_pool does not switch back to the primary once lagging is disabled.
|
12 years ago |
ckolivas
|
f71d635f0f
|
Free work before retrying in get_work_thread.
|
12 years ago |
Con Kolivas
|
b3cfe47222
|
Increment total work counter under mutex lock.
|
12 years ago |
Con Kolivas
|
e8daf1d8f2
|
Increment the queued count after the curl is popped in case there's a delay waiting on curls and we think we've queued work when in fact we're waiting on curls.
|
12 years ago |
Kano
|
b3e9858c9f
|
API new command 'coin' with mining information
|
12 years ago |
Con Kolivas
|
08948e02f3
|
Increase curl reaping time to 5 minutes since comms between curl requests can be 2 mins apart with lots of rolltime.
|
12 years ago |