c0mrade69
Newbie
 Offline
Activity: 15
Merit: 0
|
 |
April 28, 2019, 06:28:45 PM |
|
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things? To don't have to restart miner..  just asking ..  |
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
April 28, 2019, 06:59:11 PM |
|
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things? To don't have to restart miner.. just asking .. Yes, it is already on my list and will come in one of the next releases - some other user already suggested that. On easy thing that you can do to improve you hashrate quite a lot is to improve the cooling of the GPUs. This can easily bring you additional 5-10% - maybe you already noticed that a cold GPU performs much better than a hot one. |
|
|
|
|
|
dragonmike
|
|
April 28, 2019, 09:17:40 PM |
|
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things? To don't have to restart miner.. just asking .. Yes, it is already on my list and will come in one of the next releases - some other user already suggested that. On easy thing that you can do to improve you hashrate quite a lot is to improve the cooling of the GPUs. This can easily bring you additional 5-10% - maybe you already noticed that a cold GPU performs much better than a hot one. Whilst this is quite common knowledge, I think it only really starts making a difference if your GPU is around 75-80C and above. Don't think I've actually seen any performance degradation from a few degrees difference while one's cruising under 70 (where most undervolted Pascal cards should sit quite comfortably). |
|
|
|
|
c0mrade69
Newbie
Offline
Activity: 15
Merit: 0
|
|
April 28, 2019, 10:11:40 PM |
|
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things? To don't have to restart miner.. just asking .. Yes, it is already on my list and will come in one of the next releases - some other user already suggested that. On easy thing that you can do to improve you hashrate quite a lot is to improve the cooling of the GPUs. This can easily bring you additional 5-10% - maybe you already noticed that a cold GPU performs much better than a hot one. Great! my cards running relaxed on 50 degrees, so dont think the temperature is problem in my case.. |
|
|
|
|
Shaddyr
Jr. Member
Offline
Activity: 48
Merit: 2
|
|
April 29, 2019, 01:02:18 AM |
|
TrailingStop, what about statistic for shares at console - accepted\rejected etc, per device and summary?
|
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
April 29, 2019, 01:55:13 AM |
|
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things? To don't have to restart miner.. just asking .. Yes, it is already on my list and will come in one of the next releases - some other user already suggested that. On easy thing that you can do to improve you hashrate quite a lot is to improve the cooling of the GPUs. This can easily bring you additional 5-10% - maybe you already noticed that a cold GPU performs much better than a hot one. Whilst this is quite common knowledge, I think it only really starts making a difference if your GPU is around 75-80C and above. Don't think I've actually seen any performance degradation from a few degrees difference while one's cruising under 70 (where most undervolted Pascal cards should sit quite comfortably). Hi dragonmike, this is what I'm talking about - maybe that is because I do not really take too much care about the environment. This is my development 1070 in a big tower case - as you can see temp is 67°C and hashrate is around 2.2 MH/s - the miner running up for 60 seconds: 03:44:30 GPU[1]: 2.254 MH/s CClk:1.835 GHz MClk:3.898 GHz 64C 31% 173W 13.031 kH/W [A0:R0 0.0%] LastShare: - 03:44:30 Rig-Speed[2 min]: 2.254 MH/s 173W 13.031 kH/W [A0:R0 0.0%] Uptime: 00:00:59 LastShare: - 03:44:30 Luck: avg.time per share (1.074 GH @ 2.254 MH/s) 477 secs. passed 58 secs. luck share: 12% session: - 03:44:45 GPU[1]: 2.212 MH/s CClk:1.835 GHz MClk:3.898 GHz 66C 31% 173W 12.783 kH/W [A0:R0 0.0%] LastShare: - 03:44:45 Rig-Speed[2 min]: 2.212 MH/s 173W 12.783 kH/W [A0:R0 0.0%] Uptime: 00:01:14 LastShare: - 03:44:45 Luck: avg.time per share (1.074 GH @ 2.212 MH/s) 486 secs. passed 73 secs. luck share: 15% session: - 03:45:00 GPU[1]: 2.217 MH/s CClk:1.822 GHz MClk:3.898 GHz 66C 35% 174W 12.741 kH/W [A0:R0 0.0%] LastShare: - 03:45:00 Rig-Speed[2 min]: 2.217 MH/s 174W 12.741 kH/W [A0:R0 0.0%] Uptime: 00:01:29 LastShare: - 03:45:00 Luck: avg.time per share (1.074 GH @ 2.217 MH/s) 485 secs. passed 88 secs. luck share: 18% session: - 03:45:15 GPU[1]: 2.221 MH/s CClk:1.822 GHz MClk:3.898 GHz 67C 38% 174W 12.761 kH/W [A0:R0 0.0%] LastShare: - 03:45:15 Rig-Speed[2 min]: 2.221 MH/s 174W 12.761 kH/W [A0:R0 0.0%] Uptime: 00:01:44 LastShare: - 03:45:15 Luck: avg.time per share (1.074 GH @ 2.221 MH/s) 484 secs. passed 103 secs. luck share: 21% session: - After some minute the temp is up to 69°C and the hashrate is down to 2.1 MH/s and during the same timeframe the CoreClk is down from more than 1.8 GHz to 1.75GHz: 03:52:15 Rig-Speed[2 min]: 2.097 MH/s 156W 13.443 kH/W [A1:R0 0.0%] Uptime: 00:08:44 LastShare: 00:06:11 03:52:15 Luck: avg.time per share (1.074 GH @ 2.097 MH/s) 513 secs. passed 371 secs. luck share: 72% session: 31% 03:52:30 GPU[1]: 2.097 MH/s CClk:1.746 GHz MClk:3.898 GHz 69C 52% 156W 13.443 kH/W [A0:R0 0.0%] LastShare: 00:06:26 03:52:30 Rig-Speed[2 min]: 2.097 MH/s 156W 13.443 kH/W [A1:R0 0.0%] Uptime: 00:08:59 LastShare: 00:06:26 03:52:30 Luck: avg.time per share (1.074 GH @ 2.097 MH/s) 513 secs. passed 386 secs. luck share: 75% session: 31% 03:52:45 GPU[1]: 2.097 MH/s CClk:1.746 GHz MClk:3.898 GHz 69C 52% 156W 13.443 kH/W [A0:R0 0.0%] LastShare: 00:06:41 03:52:45 Rig-Speed[2 min]: 2.097 MH/s 156W 13.443 kH/W [A1:R0 0.0%] Uptime: 00:09:14 LastShare: 00:06:41 03:52:45 Luck: avg.time per share (1.074 GH @ 2.097 MH/s) 513 secs. passed 401 secs. luck share: 78% session: 31% Maybe I should take more care - have Fan on 'auto' in AB. |
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
April 29, 2019, 01:59:41 AM |
|
TrailingStop, what about statistic for shares at console - accepted\rejected etc, per device and summary?
Hi, I'm not sure what you mean with 'shares for console'  Here is what you get now: 03:56:45 GPU[3]: 4.116 MH/s CClk:1.341 GHz MClk:3.504 GHz 75C 53% [A1807:R1 0.1%] LastShare: 00:00:51 03:56:45 GPU[4]: 2.202 MH/s CClk:1.430 GHz MClk:3.003 GHz 82C 60% [A887:R1 0.1%] LastShare: 00:00:08 03:56:45 Rig-Speed[2 min]: 6.319 MH/s [A2694:R2 0.1%] Uptime: 13:56:22 LastShare: 00:00:08 03:56:45 Luck: avg.time per share (133.99 MH @ 6.319 MH/s) 22 secs. passed 8 secs. luck share: 38% session: 96% first you see the accepted/rejected shares per GPU: 03:56:45 GPU[3]: 4.116 MH/s CClk:1.341 GHz MClk:3.504 GHz 75C 53% [A1807:R1 0.1%] LastShare: 00:00:51 03:56:45 GPU[4]: 2.202 MH/s CClk:1.430 GHz MClk:3.003 GHz 82C 60% [A887:R1 0.1%] LastShare: 00:00:08 and then you get a summary: 03:56:45 Rig-Speed[2 min]: 6.319 MH/s [A2694:R2 0.1%] Uptime: 13:56:22 LastShare: 00:00:08 Can you please explain in more detail what you mean with 'shares at console - accepted\rejected etc, per device and summary' ? Thanks. |
|
|
|
|
|
dragonmike
|
|
April 29, 2019, 09:02:32 AM |
|
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things? To don't have to restart miner.. just asking .. Yes, it is already on my list and will come in one of the next releases - some other user already suggested that. On easy thing that you can do to improve you hashrate quite a lot is to improve the cooling of the GPUs. This can easily bring you additional 5-10% - maybe you already noticed that a cold GPU performs much better than a hot one. Whilst this is quite common knowledge, I think it only really starts making a difference if your GPU is around 75-80C and above. Don't think I've actually seen any performance degradation from a few degrees difference while one's cruising under 70 (where most undervolted Pascal cards should sit quite comfortably). Hi dragonmike, this is what I'm talking about - maybe that is because I do not really take too much care about the environment. This is my development 1070 in a big tower case - as you can see temp is 67°C and hashrate is around 2.2 MH/s - the miner running up for 60 seconds: 03:44:30 GPU[1]: 2.254 MH/s CClk:1.835 GHz MClk:3.898 GHz 64C 31% 173W 13.031 kH/W [A0:R0 0.0%] LastShare: - 03:44:30 Rig-Speed[2 min]: 2.254 MH/s 173W 13.031 kH/W [A0:R0 0.0%] Uptime: 00:00:59 LastShare: - 03:44:30 Luck: avg.time per share (1.074 GH @ 2.254 MH/s) 477 secs. passed 58 secs. luck share: 12% session: - 03:44:45 GPU[1]: 2.212 MH/s CClk:1.835 GHz MClk:3.898 GHz 66C 31% 173W 12.783 kH/W [A0:R0 0.0%] LastShare: - 03:44:45 Rig-Speed[2 min]: 2.212 MH/s 173W 12.783 kH/W [A0:R0 0.0%] Uptime: 00:01:14 LastShare: - 03:44:45 Luck: avg.time per share (1.074 GH @ 2.212 MH/s) 486 secs. passed 73 secs. luck share: 15% session: - 03:45:00 GPU[1]: 2.217 MH/s CClk:1.822 GHz MClk:3.898 GHz 66C 35% 174W 12.741 kH/W [A0:R0 0.0%] LastShare: - 03:45:00 Rig-Speed[2 min]: 2.217 MH/s 174W 12.741 kH/W [A0:R0 0.0%] Uptime: 00:01:29 LastShare: - 03:45:00 Luck: avg.time per share (1.074 GH @ 2.217 MH/s) 485 secs. passed 88 secs. luck share: 18% session: - 03:45:15 GPU[1]: 2.221 MH/s CClk:1.822 GHz MClk:3.898 GHz 67C 38% 174W 12.761 kH/W [A0:R0 0.0%] LastShare: - 03:45:15 Rig-Speed[2 min]: 2.221 MH/s 174W 12.761 kH/W [A0:R0 0.0%] Uptime: 00:01:44 LastShare: - 03:45:15 Luck: avg.time per share (1.074 GH @ 2.221 MH/s) 484 secs. passed 103 secs. luck share: 21% session: - After some minute the temp is up to 69°C and the hashrate is down to 2.1 MH/s and during the same timeframe the CoreClk is down from more than 1.8 GHz to 1.75GHz: 03:52:15 Rig-Speed[2 min]: 2.097 MH/s 156W 13.443 kH/W [A1:R0 0.0%] Uptime: 00:08:44 LastShare: 00:06:11 03:52:15 Luck: avg.time per share (1.074 GH @ 2.097 MH/s) 513 secs. passed 371 secs. luck share: 72% session: 31% 03:52:30 GPU[1]: 2.097 MH/s CClk:1.746 GHz MClk:3.898 GHz 69C 52% 156W 13.443 kH/W [A0:R0 0.0%] LastShare: 00:06:26 03:52:30 Rig-Speed[2 min]: 2.097 MH/s 156W 13.443 kH/W [A1:R0 0.0%] Uptime: 00:08:59 LastShare: 00:06:26 03:52:30 Luck: avg.time per share (1.074 GH @ 2.097 MH/s) 513 secs. passed 386 secs. luck share: 75% session: 31% 03:52:45 GPU[1]: 2.097 MH/s CClk:1.746 GHz MClk:3.898 GHz 69C 52% 156W 13.443 kH/W [A0:R0 0.0%] LastShare: 00:06:41 03:52:45 Rig-Speed[2 min]: 2.097 MH/s 156W 13.443 kH/W [A1:R0 0.0%] Uptime: 00:09:14 LastShare: 00:06:41 03:52:45 Luck: avg.time per share (1.074 GH @ 2.097 MH/s) 513 secs. passed 401 secs. luck share: 78% session: 31% Maybe I should take more care - have Fan on 'auto' in AB. No this is a fair observation. If you start throttling between 67 and 69C it's definitely more sensitive than other miners/algos so worth pointing out. I'll try setting a more aggressive fan curve, or pay closer attention to speeds between the cards next time, to see if there's any noticeable differences. |
|
|
|
|
Shaddyr
Jr. Member
Offline
Activity: 48
Merit: 2
|
|
April 29, 2019, 10:47:32 AM |
|
TrailingStop, what about statistic for shares at console - accepted\rejected etc, per device and summary?
Hi, I'm not sure what you mean with 'shares for console' Here is what you get now: 03:56:45 GPU[3]: 4.116 MH/s CClk:1.341 GHz MClk:3.504 GHz 75C 53% [A1807:R1 0.1%] LastShare: 00:00:51 03:56:45 GPU[4]: 2.202 MH/s CClk:1.430 GHz MClk:3.003 GHz 82C 60% [A887:R1 0.1%] LastShare: 00:00:08 03:56:45 Rig-Speed[2 min]: 6.319 MH/s [A2694:R2 0.1%] Uptime: 13:56:22 LastShare: 00:00:08 03:56:45 Luck: avg.time per share (133.99 MH @ 6.319 MH/s) 22 secs. passed 8 secs. luck share: 38% session: 96% first you see the accepted/rejected shares per GPU: 03:56:45 GPU[3]: 4.116 MH/s CClk:1.341 GHz MClk:3.504 GHz 75C 53% [A1807:R1 0.1%] LastShare: 00:00:51 03:56:45 GPU[4]: 2.202 MH/s CClk:1.430 GHz MClk:3.003 GHz 82C 60% [A887:R1 0.1%] LastShare: 00:00:08 and then you get a summary: 03:56:45 Rig-Speed[2 min]: 6.319 MH/s [A2694:R2 0.1%] Uptime: 13:56:22 LastShare: 00:00:08 Can you please explain in more detail what you mean with 'shares at console - accepted\rejected etc, per device and summary' ? Thanks. That's it. I just now understood these codes. Maybe you should bring it out more intuitive? |
|
|
|
|
impynick
Jr. Member
Offline
Activity: 77
Merit: 6
|
|
May 02, 2019, 09:33:55 AM |
|
Hi TrailingStop Big fan, where can I send you a crash dump file? About to test out autotune feature  |
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 08, 2019, 08:41:31 PM |
|
Hi TrailingStop Big fan, where can I send you a crash dump file? About to test out autotune feature Send you a DM some days ago...please check. |
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 08, 2019, 08:47:49 PM
Last edit: May 08, 2019, 10:15:00 PM by TrailingStop |
|
New version 2.2.3 release.
These are the modification - I have had to modify some of the core functions so that they become OS independent. So please check if this version works as expected. If not please reinstall 2.2.2 and report the issues to me so that I can fix them.
- Fixed a file sharing bug.
- Changed Thread-functions to be OS independent.
- Changed File I/O to be OS independent.
- Fixed a the time-interval for updatechecks.
- Shows information how long the Merkle Tree generation took (MTP only).
- Shows the current mining block if the information was available in mining notify.
- Shows optimized grid- and blocksize that is used for the Kernel.
- Add power usage information into API information. Requires Awesome Miner Version 6.3.4 or later.
- ProgPoW: Show when a new algo is created (New Epoch for BCI, otherwise after 50 block).
- ProgPoW: Calculate optimized blocksize for each new algo.
- ProgPoW: Add version used by Zano (Cuda 10.1 only - older cuda versions will follow soon).
- ProgPoW/MTP: Small performance improvements.
Happy mining!
|
|
|
|
|
algunnombre
Newbie
Offline
Activity: 36
Merit: 0
|
|
May 08, 2019, 10:08:03 PM |
|
New version 2.2.3 release.
These are the modification - I have had to modify some of the core functions so that they become OS independent. So please check if this version works as expected. If not please reinstall 2.2.2 and report the issues to me so that I can fix them.
- Fixed a file sharing bug.
- Changed Thread-functions to be OS independent.
- Changed File I/O to be OS independent.
- Fixed a the time-interval for updatechecks.
- Shows information how long the Merkle Tree generation took (MTP only).
- Shows the current mining block if the information was available in mining notify.
- Shows optimized grid- and blocksize that is used for the Kernel.
- Add power usage information into API information. Requires Awesome Miner Version 6.3.4 or later.
- ProgPoW: Show when a new algo is created (New Epoch for BCI, otherwise after 50 block).
- ProgPoW: Calculate optimized blocksize for each new algo.
- ProgPoW: Add version used by Zano.
- ProgPoW/MTP: Small performance improvements.
Happy mining!
Thanks for the update. Any recommended configuration for 1080ti rig on MTP? is it better to just run the miner with -i 15 or -i auto 1024 8192 256? |
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 08, 2019, 10:14:09 PM |
|
Thanks for the update.
Any recommended configuration for 1080ti rig? is it better to just run the miner with -i 15 or -i auto 1024 8192 256?
Are you on MTP? To find the best settings I would start without OC and run default intensity. As soon as the hashrate is stable I would increase intensity. Repeat that until you do not see higher hashrates. Then use the best intensity. After that you can play with some OC and see if that have any impact to your system. Sorry that I do not have a more 'concrete' advice, but systems are too different to give general hints that fits all of them. |
|
|
|
|
arielbit
Legendary
Offline
Activity: 3444
Merit: 1061
|
|
May 08, 2019, 10:23:23 PM |
|
New version 2.2.3 release.
These are the modification - I have had to modify some of the core functions so that they become OS independent. So please check if this version works as expected. If not please reinstall 2.2.2 and report the issues to me so that I can fix them.
- Fixed a file sharing bug.
- Changed Thread-functions to be OS independent.
- Changed File I/O to be OS independent.
- Fixed a the time-interval for updatechecks.
- Shows information how long the Merkle Tree generation took (MTP only).
- Shows the current mining block if the information was available in mining notify.
- Shows optimized grid- and blocksize that is used for the Kernel.
- Add power usage information into API information. Requires Awesome Miner Version 6.3.4 or later.
- ProgPoW: Show when a new algo is created (New Epoch for BCI, otherwise after 50 block).
- ProgPoW: Calculate optimized blocksize for each new algo.
- ProgPoW: Add version used by Zano (Cuda 10.1 only - older cuda versions will follow soon).
- ProgPoW/MTP: Small performance improvements.
Happy mining!
progpow-zano is unstable, (2 out of 3 GPUs) and (1 out of 2)will stop mining around 20-30mins (not crash it just stops) windows 7 64bit, cuda 10.1 |
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 08, 2019, 10:29:48 PM |
|
New version 2.2.3 release.
These are the modification - I have had to modify some of the core functions so that they become OS independent. So please check if this version works as expected. If not please reinstall 2.2.2 and report the issues to me so that I can fix them.
- Fixed a file sharing bug.
- Changed Thread-functions to be OS independent.
- Changed File I/O to be OS independent.
- Fixed a the time-interval for updatechecks.
- Shows information how long the Merkle Tree generation took (MTP only).
- Shows the current mining block if the information was available in mining notify.
- Shows optimized grid- and blocksize that is used for the Kernel.
- Add power usage information into API information. Requires Awesome Miner Version 6.3.4 or later.
- ProgPoW: Show when a new algo is created (New Epoch for BCI, otherwise after 50 block).
- ProgPoW: Calculate optimized blocksize for each new algo.
- ProgPoW: Add version used by Zano (Cuda 10.1 only - older cuda versions will follow soon).
- ProgPoW/MTP: Small performance improvements.
Happy mining!
progpow-zano is unstable, (2 out of 3 GPUs) and (1 out of 2)will stop mining/crash around 20-30mins windows 7 64bit, cuda 10.1 Hi, there was just a new Zano release (daemon/GUI). I just read that there will be new binaries. So please wait until this update is finished and please download TT again and retry. Please add -log -logpool to your commandline to create logfiles. If it crashes again please send me the log - they can help me to find the problem. Thanks for reporting. |
|
|
|
|
algunnombre
Newbie
Offline
Activity: 36
Merit: 0
|
|
May 08, 2019, 10:30:44 PM |
|
Thanks for the update.
Any recommended configuration for 1080ti rig? is it better to just run the miner with -i 15 or -i auto 1024 8192 256?
Are you on MTP? To find the best settings I would start without OC and run default intensity. As soon as the hashrate is stable I would increase intensity. Repeat that until you do not see higher hashrates. Then use the best intensity. After that you can play with some OC and see if that have any impact to your system. Sorry that I do not have a more 'concrete' advice, but systems are too different to give general hints that fits all of them. Thanks for the quick reply, yeah I'm on MTP, just wanted te see if there was a tested base point to start off. about my other question, which type of intensity would you recommend tu use a) -i 14, b) -i auto 1024 8192 256, c) -gi,gs ? thanks |
|
|
|
|
TrailingStop (OP)
Member
Offline
Activity: 566
Merit: 16
|
|
May 08, 2019, 10:35:26 PM |
|
Thanks for the update.
Any recommended configuration for 1080ti rig? is it better to just run the miner with -i 15 or -i auto 1024 8192 256?
Are you on MTP? To find the best settings I would start without OC and run default intensity. As soon as the hashrate is stable I would increase intensity. Repeat that until you do not see higher hashrates. Then use the best intensity. After that you can play with some OC and see if that have any impact to your system. Sorry that I do not have a more 'concrete' advice, but systems are too different to give general hints that fits all of them. Thanks for the quick reply, yeah I'm on MTP, just wanted te see if there was a tested base point to start off. about my other question, which type of intensity would you recommend tu use a) -i 14, b) -i auto 1024 8192 256, c) -gi,gs ? thanks I would start without -i. The miner will tell you which default intensity it uses for your gpu. Then wait for a stable hashrate and restart with a higher intensity (-i) until you see that it doesn't rise anymore. -i auto takes a very long time (and please do not forget to add -log to your command line so that you can see the best settings for your gpu.) I general I assume that the sweet point is default intensity + 1 or +2 - just in case you want to have a fast result. |
|
|
|
|
algunnombre
Newbie
Offline
Activity: 36
Merit: 0
|
|
May 09, 2019, 12:10:47 AM |
|
Thanks for the update.
Any recommended configuration for 1080ti rig? is it better to just run the miner with -i 15 or -i auto 1024 8192 256?
Are you on MTP? To find the best settings I would start without OC and run default intensity. As soon as the hashrate is stable I would increase intensity. Repeat that until you do not see higher hashrates. Then use the best intensity. After that you can play with some OC and see if that have any impact to your system. Sorry that I do not have a more 'concrete' advice, but systems are too different to give general hints that fits all of them. Thanks for the quick reply, yeah I'm on MTP, just wanted te see if there was a tested base point to start off. about my other question, which type of intensity would you recommend tu use a) -i 14, b) -i auto 1024 8192 256, c) -gi,gs ? thanks I would start without -i. The miner will tell you which default intensity it uses for your gpu. Then wait for a stable hashrate and restart with a higher intensity (-i) until you see that it doesn't rise anymore. -i auto takes a very long time (and please do not forget to add -log to your command line so that you can see the best settings for your gpu.) I general I assume that the sweet point is default intensity + 1 or +2 - just in case you want to have a fast result. awesome thanks |
|
|
|
|
MiningTaken
Newbie
Offline
Activity: 28
Merit: 0
|
|
May 09, 2019, 02:01:02 AM |
|
New version 2.2.3 release.
These are the modification - I have had to modify some of the core functions so that they become OS independent. So please check if this version works as expected. If not please reinstall 2.2.2 and report the issues to me so that I can fix them.
- Fixed a file sharing bug.
- Changed Thread-functions to be OS independent.
- Changed File I/O to be OS independent.
- Fixed a the time-interval for updatechecks.
- Shows information how long the Merkle Tree generation took (MTP only).
- Shows the current mining block if the information was available in mining notify.
- Shows optimized grid- and blocksize that is used for the Kernel.
- Add power usage information into API information. Requires Awesome Miner Version 6.3.4 or later.
- ProgPoW: Show when a new algo is created (New Epoch for BCI, otherwise after 50 block).
- ProgPoW: Calculate optimized blocksize for each new algo.
- ProgPoW: Add version used by Zano (Cuda 10.1 only - older cuda versions will follow soon).
- ProgPoW/MTP: Small performance improvements.
Happy mining!
Hi. Any change on "-b" or "--api-bind" arguments, so it can be accessed from other computer in same network (not just from rig's local computer)? Thanks. |
|
|
|
|
|
