I will focus now on improving default device settings, including memory timings, and X16R/X16S.
I am planning a complete rewrite of the X16R/X16S kernels.
Stay tuned!
Topic: Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480! - page 36. (Read 214428 times)
Gateless Gate Sharp 1.3.4 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.4-alpha
* Fixed critical bugs with CryptoNight variants.
* Removed optional OpenCL binaries.
Phew!
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.4-alpha
* Fixed critical bugs with CryptoNight variants.
* Removed optional OpenCL binaries.
Phew!
Gateless Gate Sharp 1.3.3 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.3-alpha
* Added full support for CryptoNightV7, CryptoNight-Heavy, CryptoNight-Light, X16R, and X16S.
* Added support for Raven, Pigeoncoin, Sumokoin, and AEON.
* Added new default pools including Mining Pool Hub.
* Updated default device settings.
* Improved device settings handling, benchmarking, and optimization.
* Numerous bug fixes and improvements.
Hope this version is worth the wait. Enjoy!
Hi!https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.3-alpha
* Added full support for CryptoNightV7, CryptoNight-Heavy, CryptoNight-Light, X16R, and X16S.
* Added support for Raven, Pigeoncoin, Sumokoin, and AEON.
* Added new default pools including Mining Pool Hub.
* Updated default device settings.
* Improved device settings handling, benchmarking, and optimization.
* Numerous bug fixes and improvements.
Hope this version is worth the wait. Enjoy!
I cannot mine Haven coin (CryptoNight-Heavy)... Devices - RX 560 2Gb, OS - Win10 64. Pool - haven.miner.rocks.
See http://sendfile.su/1413532
ok ok, I miss to select "custom pool" in the dashboard menu.....
Rx580 ethereum mod(1click srbpolaris) is giving me 963 H/s with intensity 144, ws 8,2 threads. Haven't touched memory & core overclock from ethereum and timing with optimization as I don't know how to do it properly.
So, for the moment, those rx 580 rigs will be happy to mine monero.
x16r: sg miner configuration for rx 580 was ())) -g 2 --thread-concurrency 1792 I 19.
I don't know how to translate it in ggs but I will try tonight
The Baffin rigs, that have a small ssd and an hdd, are giving error 761 when I try to install GGS in the HDD (d:\) or in the SSD and then restart, error, restart, till I kill it.
I am not in a rush, as I'm mining turtlecoin there (cryptonight lite v7 that you do't support
yet) waiting for AEON, but I would like, one day or another, to run a full optimize on the baffin as I know speed can be much higher.
I know turtlecoin is a satoshi coin... but they are friends
Any suggestion on the 761 error ?
Rx580 ethereum mod(1click srbpolaris) is giving me 963 H/s with intensity 144, ws 8,2 threads. Haven't touched memory & core overclock from ethereum and timing with optimization as I don't know how to do it properly.
So, for the moment, those rx 580 rigs will be happy to mine monero.
x16r: sg miner configuration for rx 580 was (
))) -g 2 --thread-concurrency 1792 I 19.I don't know how to translate it in ggs but I will try tonight
The Baffin rigs, that have a small ssd and an hdd, are giving error 761 when I try to install GGS in the HDD (d:\) or in the SSD and then restart, error, restart, till I kill it.
I am not in a rush, as I'm mining turtlecoin there (cryptonight lite v7 that you do't support
yet) waiting for AEON, but I would like, one day or another, to run a full optimize on the baffin as I know speed can be much higher.I know turtlecoin is a satoshi coin... but they are friends
Any suggestion on the 761 error ?
Hi found a problem. Grabbed 1.3.3 alpha. Mining Stellite. After coming off DEVFEE, version of Cryptonight doesn't switch back so after DEVFEE finishes, no shares are submitted, at all. Here's snippet of log. You can see it switches from Monero version 3 to Monero version 7 for DEVFEE, but never switches back. I have to restart it before I get any new shares:
Code:
2018-04-15 10:43:11.8818 [1] Gateless Gate Sharp 1.3.3 alpha started.
2018-04-15 10:43:12.6787 [1] Number of Devices: 6
2018-04-15 10:43:12.7256 [1] Successfully initialized AMD Display Library.
2018-04-15 10:43:12.7256 [1] Number of ADL Adapters: 46
2018-04-15 10:43:12.7725 [1] ADL_Adapter_AdapterInfo_Get() returned error code 0
2018-04-15 10:43:12.7725 [1] Failed to initialize NVIDIA Management Library.
2018-04-15 10:43:21.7113 [1] Loaded PhyMem.
2018-04-15 10:43:27.5847 [1] Loaded DeviceSettings\AMD Radeon RX 470 4.0GB.xml for Device #0.
2018-04-15 10:43:37.4451 [1] Loaded DeviceSettings\AMD Radeon RX 470 4.0GB.xml for Device #2.
2018-04-15 10:43:46.8876 [1] Loaded DeviceSettings\AMD Radeon RX 470 4.0GB.xml for Device #3.
2018-04-15 10:43:56.1855 [1] Loaded DeviceSettings\AMD Radeon RX 470 4.0GB.xml for Device #4.
2018-04-15 10:43:57.0450 [1] Unloaded PhyMem.
2018-04-15 10:43:57.0606 [1] Invalid argument: C:\Users\James Simmons\Downloads\Gateless Gate Sharp\GatelessGateSharp.exe
2018-04-15 10:44:01.2017 [13] Running garbage collection...
2018-04-15 10:44:01.2017 [13] Memory used before collection: 138MB
2018-04-15 10:44:01.2798 [13] Memory used before collection: 25MB
2018-04-15 10:44:03.2019 [15] API Listener started.
2018-04-15 10:46:29.9988 [1] Saving settings to C:\Users\James Simmons\AppData\Roaming\GatelessGateSharp\GatelessGateSharp.sqlite...
2018-04-15 10:46:30.2332 [1] Saved settings.
2018-04-15 10:46:30.2645 [1] Launching miner(s) for Custom Pool 0...
2018-04-15 10:46:30.5927 [16] Miner thread for Device #0 started.
2018-04-15 10:46:30.5927 [16] NiceHash mode is off.
2018-04-15 10:46:30.6084 [16] Loaded Kernels\cryptonight.cl for Device #0.
2018-04-15 10:46:31.4209 [17] Miner thread for Device #0 started.
2018-04-15 10:46:31.4209 [17] NiceHash mode is off.
2018-04-15 10:46:31.4209 [17] Loaded Kernels\cryptonight.cl for Device #0.
2018-04-15 10:46:32.2960 [18] Miner thread for Device #1 started.
2018-04-15 10:46:32.2960 [18] NiceHash mode is off.
2018-04-15 10:46:32.2960 [18] Loaded Kernels\cryptonight.cl for Device #1.
2018-04-15 10:46:33.1086 [19] Miner thread for Device #1 started.
2018-04-15 10:46:33.1086 [19] NiceHash mode is off.
2018-04-15 10:46:33.1242 [19] Loaded Kernels\cryptonight.cl for Device #1.
2018-04-15 10:46:35.1869 [20] Miner thread for Device #2 started.
2018-04-15 10:46:35.1869 [20] NiceHash mode is off.
2018-04-15 10:46:35.1869 [16] Built cryptonight program for Device #0.
2018-04-15 10:46:35.1869 [16] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:35.2025 [20] Loaded Kernels\cryptonight.cl for Device #2.
[color=yellow]2018-04-15 10:46:35.2025 [16] Switching to Monero Version 3[/color]
2018-04-15 10:46:36.0307 [21] Miner thread for Device #2 started.
2018-04-15 10:46:36.0307 [21] NiceHash mode is off.
2018-04-15 10:46:36.0307 [21] Loaded Kernels\cryptonight.cl for Device #2.
2018-04-15 10:46:38.1502 [22] Miner thread for Device #3 started.
2018-04-15 10:46:38.1502 [22] NiceHash mode is off.
2018-04-15 10:46:38.1502 [19] Built cryptonight program for Device #1.
2018-04-15 10:46:38.1502 [19] Build options: -O5 -legacy -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:38.1502 [19] Switching to Monero Version 3
2018-04-15 10:46:38.1658 [22] Loaded Kernels\cryptonight.cl for Device #3.
2018-04-15 10:46:38.9784 [23] Miner thread for Device #3 started.
2018-04-15 10:46:38.9784 [23] NiceHash mode is off.
2018-04-15 10:46:38.9784 [23] Loaded Kernels\cryptonight.cl for Device #3.
2018-04-15 10:46:42.7913 [24] Miner thread for Device #4 started.
2018-04-15 10:46:42.7913 [24] NiceHash mode is off.
2018-04-15 10:46:42.7913 [21] Built cryptonight program for Device #2.
2018-04-15 10:46:42.7913 [21] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:42.7913 [21] Switching to Monero Version 3
2018-04-15 10:46:42.7913 [24] Loaded Kernels\cryptonight.cl for Device #4.
2018-04-15 10:46:43.6039 [25] Miner thread for Device #4 started.
2018-04-15 10:46:43.6039 [25] NiceHash mode is off.
2018-04-15 10:46:43.6039 [25] Loaded Kernels\cryptonight.cl for Device #4.
2018-04-15 10:46:44.9478 [16] Device #0 submitted Share #0 to communitypool.stellite.cash as Se2xy7zgW....
2018-04-15 10:46:44.9478 [16] Device #0 submitted a share to communitypool.stellite.cash as Se2xy7zgW....
2018-04-15 10:46:45.1666 [9] Share #0 accepted.
2018-04-15 10:46:45.2291 [26] Miner thread for Device #5 started.
2018-04-15 10:46:45.2291 [26] NiceHash mode is off.
2018-04-15 10:46:45.2447 [26] Loaded Kernels\cryptonight.cl for Device #5.
2018-04-15 10:46:46.0573 [27] Miner thread for Device #5 started.
2018-04-15 10:46:46.0573 [27] NiceHash mode is off.
2018-04-15 10:46:46.0573 [27] Loaded Kernels\cryptonight.cl for Device #5.
2018-04-15 10:46:46.5417 [16] Device #0 (CryptoNight): 558.70 h/s
2018-04-15 10:46:47.2606 [23] Built cryptonight program for Device #3.
2018-04-15 10:46:47.2606 [23] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:47.2606 [23] Switching to Monero Version 3
2018-04-15 10:46:49.3389 [19] Device #1 (CryptoNight): 360.80 h/s
2018-04-15 10:46:49.9171 [27] Built cryptonight program for Device #5.
2018-04-15 10:46:49.9171 [27] Build options: -O5 -legacy -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:49.9171 [27] Switching to Monero Version 3
2018-04-15 10:46:50.8391 [9] Received new job: h81JaI/iTTSABw1vZOjh1+ORJg5w
2018-04-15 10:46:52.5893 [26] Built cryptonight program for Device #5.
2018-04-15 10:46:52.5893 [26] Build options: -O5 -legacy -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:52.5893 [26] Switching to Monero Version 3
2018-04-15 10:46:54.2145 [21] Device #2 (CryptoNight): 555.02 h/s
2018-04-15 10:46:56.9492 [25] Built cryptonight program for Device #4.
2018-04-15 10:46:56.9492 [25] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:46:56.9492 [25] Switching to Monero Version 3
2018-04-15 10:46:57.7773 [16] Device #0 (CryptoNight): 558.65 h/s
2018-04-15 10:46:58.6681 [23] Device #3 (CryptoNight): 554.60 h/s
2018-04-15 10:47:00.4964 [19] Device #1 (CryptoNight): 362.37 h/s
2018-04-15 10:47:01.5278 [27] Device #5 (CryptoNight): 226.17 h/s
2018-04-15 10:47:01.8559 [24] Built cryptonight program for Device #4.
2018-04-15 10:47:01.8559 [24] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:01.8559 [24] Switching to Monero Version 3
2018-04-15 10:47:03.4498 [26] Device #5 (CryptoNight): 226.17 h/s
2018-04-15 10:47:05.5125 [21] Device #2 (CryptoNight): 554.71 h/s
2018-04-15 10:47:06.7002 [22] Built cryptonight program for Device #3.
2018-04-15 10:47:06.7002 [22] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:06.7002 [22] Switching to Monero Version 3
2018-04-15 10:47:07.6378 [25] Device #4 (CryptoNight): 316.43 h/s
2018-04-15 10:47:09.0129 [16] Device #0 (CryptoNight): 558.26 h/s
2018-04-15 10:47:09.6536 [23] Device #3 (CryptoNight): 308.67 h/s
2018-04-15 10:47:11.6539 [19] Device #1 (CryptoNight): 361.56 h/s
2018-04-15 10:47:11.9195 [20] Built cryptonight program for Device #2.
2018-04-15 10:47:11.9195 [20] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:11.9195 [20] Switching to Monero Version 3
2018-04-15 10:47:13.4196 [27] Device #5 (CryptoNight): 226.20 h/s
2018-04-15 10:47:13.6697 [24] Device #4 (CryptoNight): 308.10 h/s
2018-04-15 10:47:14.5604 [18] Built cryptonight program for Device #1.
2018-04-15 10:47:14.5604 [18] Build options: -O5 -legacy -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:14.5604 [18] Switching to Monero Version 3
2018-04-15 10:47:15.3417 [26] Device #5 (CryptoNight): 225.79 h/s
2018-04-15 10:47:17.7170 [21] Device #2 (CryptoNight): 316.14 h/s
2018-04-15 10:47:18.4827 [22] Device #3 (CryptoNight): 308.10 h/s
2018-04-15 10:47:18.9046 [25] Device #4 (CryptoNight): 317.28 h/s
2018-04-15 10:47:18.9358 [17] Built cryptonight program for Device #0.
2018-04-15 10:47:18.9358 [17] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-15 10:47:18.9358 [17] Switching to Monero Version 3
2018-04-15 10:47:20.2797 [16] Device #0 (CryptoNight): 543.69 h/s
2018-04-15 10:47:20.9518 [23] Device #3 (CryptoNight): 318.14 h/s
2018-04-15 10:47:21.9675 [19] Device #1 (CryptoNight): 204.98 h/s
2018-04-15 10:47:23.7333 [20] Device #2 (CryptoNight): 308.10 h/s
2018-04-15 10:47:25.2646 [24] Device #4 (CryptoNight): 309.70 h/s
2018-04-15 10:47:25.3115 [27] Device #5 (CryptoNight): 226.80 h/s
2018-04-15 10:47:26.2805 [18] Device #1 (CryptoNight): 204.75 h/s
2018-04-15 10:47:27.2337 [26] Device #5 (CryptoNight): 225.98 h/s
2018-04-15 10:47:28.9682 [21] Device #2 (CryptoNight): 318.25 h/s
2018-04-15 10:47:30.0777 [22] Device #3 (CryptoNight): 309.59 h/s
2018-04-15 10:47:30.2184 [25] Device #4 (CryptoNight): 316.19 h/s
2018-04-15 10:47:31.5935 [17] Device #0 (CryptoNight): 320.18 h/s
2018-04-15 10:47:31.9998 [16] Device #0 (CryptoNight): 309.16 h/s
2018-04-15 10:47:32.2655 [23] Device #3 (CryptoNight): 316.83 h/s
2018-04-15 10:47:32.8905 [19] Device #1 (CryptoNight): 204.90 h/s
2018-04-15 10:47:35.3438 [20] Device #2 (CryptoNight): 308.95 h/s
2018-04-15 10:47:36.8128 [24] Device #4 (CryptoNight): 310.67 h/s
2018-04-15 10:47:37.1878 [27] Device #5 (CryptoNight): 226.20 h/s
2018-04-15 10:47:37.2347 [18] Device #1 (CryptoNight): 204.23 h/s
2018-04-15 10:47:37.7817 [16] Device #0 submitted Share #1 to communitypool.stellite.cash as Se2xy7zgW....
2018-04-15 10:47:37.7817 [16] Device #0 submitted a share to communitypool.stellite.cash as Se2xy7zgW....
2018-04-15 10:47:37.9692 [9] Share #1 accepted.
2018-04-15 10:47:39.1256 [26] Device #5 (CryptoNight): 225.91 h/s
2018-04-15 10:47:40.2663 [21] Device #2 (CryptoNight): 316.64 h/s
2018-04-15 10:47:41.5790 [25] Device #4 (CryptoNight): 315.25 h/s
2018-04-15 12:05:27.6441 [1] Switching to the DEVFEE mode...
2018-04-15 12:05:27.6753 [27] Restarting miner thread...
2018-04-15 12:05:27.7222 [13] Device #0 (CryptoNight): 314.37 h/s
2018-04-15 12:05:27.7222 [13] Restarting miner thread...
[color=yellow]2018-04-15 12:05:27.9567 [13] Switching to Monero Version 7[/color]
2018-04-15 12:05:28.0192 [27] Switching to Monero Version 7
2018-04-15 12:05:28.1598 [23] Switching to Monero Version 7
2018-04-15 12:05:28.2223 [30] Device #5 (CryptoNight): 233.19 h/s
2018-04-15 12:05:28.2223 [30] Switching to Monero Version 7
2018-04-15 12:05:28.3630 [29] Switching to Monero Version 7
2018-04-15 12:05:28.4723 [26] Switching to Monero Version 7
2018-04-15 12:05:28.5974 [18] Switching to Monero Version 7
2018-04-15 12:05:28.6442 [20] Device #1 (CryptoNight): 202.53 h/s
2018-04-15 12:05:28.6442 [20] Switching to Monero Version 7
2018-04-15 12:05:28.8474 [28] Device #4 (CryptoNight): 347.24 h/s
2018-04-15 12:05:28.8474 [28] Switching to Monero Version 7
2018-04-15 12:05:28.9724 [15] Switching to Monero Version 7
2018-04-15 12:05:29.6287 [24] Device #2 (CryptoNight): 312.96 h/s
2018-04-15 12:05:29.6287 [24] Switching to Monero Version 7
2018-04-15 12:05:29.8631 [25] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:05:29.8631 [25] Switching to Monero Version 7
2018-04-15 12:05:31.3320 [26] Device #3 submitted a share to xmr-us-east1.nanopool.org as a DEVFEE.
2018-04-15 12:05:31.3320 [26] Device #3 submitted a share to xmr-us-east1.nanopool.org as a DEVFEE.
2018-04-15 12:05:31.3320 [26] Device #3 (CryptoNight): 312.98 h/s
2018-04-15 12:05:31.5508 [32] Share accepted.
2018-04-15 12:05:32.2071 [29] Device #5 (CryptoNight): 233.18 h/s
2018-04-15 12:05:32.9885 [18] Device #1 (CryptoNight): 204.64 h/s
2018-04-15 12:05:33.8947 [23] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:05:34.7074 [15] Device #0 (CryptoNight): 312.45 h/s
2018-04-15 12:05:39.3016 [13] Device #0 (CryptoNight): 315.69 h/s
2018-04-15 12:05:39.3797 [27] Device #4 (CryptoNight): 314.90 h/s
2018-04-15 12:05:39.5985 [20] Device #1 (CryptoNight): 204.57 h/s
2018-04-15 12:05:39.7392 [30] Device #5 (CryptoNight): 233.14 h/s
2018-04-15 12:05:40.3955 [28] Device #4 (CryptoNight): 310.74 h/s
2018-04-15 12:05:41.0831 [24] Device #2 (CryptoNight): 312.92 h/s
2018-04-15 12:05:41.3175 [25] Device #3 (CryptoNight): 312.95 h/s
2018-04-15 12:05:42.7864 [26] Device #3 (CryptoNight): 312.92 h/s
2018-04-15 12:05:43.7240 [29] Device #5 (CryptoNight): 232.93 h/s
2018-04-15 12:05:43.9428 [18] Device #1 (CryptoNight): 204.74 h/s
2018-04-15 12:05:45.3492 [23] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:05:46.1617 [15] Device #0 (CryptoNight): 312.27 h/s
2018-04-15 12:05:50.5372 [20] Device #1 (CryptoNight): 205.35 h/s
2018-04-15 12:05:50.6622 [13] Device #0 (CryptoNight): 315.37 h/s
2018-04-15 12:05:50.7715 [27] Device #4 (CryptoNight): 314.48 h/s
2018-04-15 12:05:50.9591 [32] Received new job: 4817
2018-04-15 12:05:51.2717 [30] Device #5 (CryptoNight): 233.19 h/s
2018-04-15 12:05:51.9124 [28] Device #4 (CryptoNight): 311.40 h/s
2018-04-15 12:05:52.5217 [24] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:05:52.7562 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:05:54.2407 [26] Device #3 (CryptoNight): 312.76 h/s
2018-04-15 12:05:54.8971 [18] Device #1 (CryptoNight): 204.52 h/s
2018-04-15 12:05:55.2565 [29] Device #5 (CryptoNight): 233.16 h/s
2018-04-15 12:05:56.4753 [27] Device #4 submitted a share to xmr-us-east1.nanopool.org as a DEVFEE.
2018-04-15 12:05:56.4753 [27] Device #4 submitted a share to xmr-us-east1.nanopool.org as a DEVFEE.
2018-04-15 12:05:56.6628 [32] Share accepted.
[color=orange]2018-04-15 12:06:27.6506 [1] Switching back from the DEVFEE mode...[/color]
2018-04-15 12:06:27.7443 [18] Device #1 (CryptoNight): 203.13 h/s
2018-04-15 12:06:28.5882 [26] Device #3 (CryptoNight): 312.82 h/s
2018-04-15 12:06:29.8382 [29] Device #5 (CryptoNight): 233.18 h/s
2018-04-15 12:06:30.5728 [12] Received new job: 6kwKoZg81V4326woKS+swufMYJ8m
2018-04-15 12:06:31.1509 [23] Device #2 (CryptoNight): 313.06 h/s
2018-04-15 12:06:31.8541 [15] Device #0 (CryptoNight): 313.84 h/s
2018-04-15 12:06:34.3544 [20] Device #1 (CryptoNight): 205.14 h/s
2018-04-15 12:06:36.2140 [13] Device #0 (CryptoNight): 314.48 h/s
2018-04-15 12:06:36.4796 [27] Device #4 (CryptoNight): 313.06 h/s
2018-04-15 12:06:37.3704 [30] Device #5 (CryptoNight): 233.30 h/s
2018-04-15 12:06:37.8392 [28] Device #4 (CryptoNight): 312.62 h/s
2018-04-15 12:06:38.3392 [24] Device #2 (CryptoNight): 313.02 h/s
2018-04-15 12:06:38.5580 [25] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:06:38.7143 [18] Device #1 (CryptoNight): 203.98 h/s
2018-04-15 12:06:39.2612 [12] Received new job: TjuVcz7aiXSYG7mFJVc+Ayh3mtfK
2018-04-15 12:06:40.0425 [26] Device #3 (CryptoNight): 312.81 h/s
2018-04-15 12:06:41.3552 [29] Device #5 (CryptoNight): 233.16 h/s
2018-04-15 12:06:42.6053 [23] Device #2 (CryptoNight): 313.04 h/s
2018-04-15 12:06:43.2616 [15] Device #0 (CryptoNight): 314.93 h/s
2018-04-15 12:06:45.3087 [20] Device #1 (CryptoNight): 204.91 h/s
2018-04-15 12:06:47.6215 [13] Device #0 (CryptoNight): 314.81 h/s
2018-04-15 12:06:47.9184 [27] Device #4 (CryptoNight): 313.50 h/s
2018-04-15 12:06:48.9028 [30] Device #5 (CryptoNight): 233.34 h/s
2018-04-15 12:06:49.2935 [28] Device #4 (CryptoNight): 312.66 h/s
2018-04-15 12:06:49.6529 [18] Device #1 (CryptoNight): 204.17 h/s
2018-04-15 12:06:49.7936 [24] Device #2 (CryptoNight): 312.92 h/s
2018-04-15 12:06:50.0123 [25] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:06:51.4968 [26] Device #3 (CryptoNight): 313.19 h/s
2018-04-15 12:06:52.8876 [29] Device #5 (CryptoNight): 232.97 h/s
2018-04-15 12:06:54.0597 [23] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:06:54.6847 [15] Device #0 (CryptoNight): 313.86 h/s
2018-04-15 12:06:56.2630 [20] Device #1 (CryptoNight): 204.73 h/s
2018-04-15 12:06:59.0289 [13] Device #0 (CryptoNight): 314.26 h/s
2018-04-15 12:06:59.3571 [27] Device #4 (CryptoNight): 313.27 h/s
2018-04-15 12:07:00.4197 [30] Device #5 (CryptoNight): 233.13 h/s
2018-04-15 12:07:00.6072 [18] Device #1 (CryptoNight): 204.60 h/s
2018-04-15 12:07:00.7635 [28] Device #4 (CryptoNight): 312.66 h/s
2018-04-15 12:07:01.2479 [24] Device #2 (CryptoNight): 313.02 h/s
2018-04-15 12:07:01.4666 [25] Device #3 (CryptoNight): 312.91 h/s
2018-04-15 12:07:02.9356 [26] Device #3 (CryptoNight): 313.33 h/s
2018-04-15 12:07:04.4044 [29] Device #5 (CryptoNight): 233.15 h/s
2018-04-15 12:07:05.5140 [23] Device #2 (CryptoNight): 312.54 h/s
2018-04-15 12:07:06.0921 [15] Device #0 (CryptoNight): 313.39 h/s
2018-04-15 12:07:07.2173 [20] Device #1 (CryptoNight): 204.53 h/s
2018-04-15 12:07:10.4364 [13] Device #0 (CryptoNight): 313.49 h/s
2018-04-15 12:07:10.8115 [27] Device #4 (CryptoNight): 313.05 h/s
2018-04-15 12:07:11.5459 [18] Device #1 (CryptoNight): 204.63 h/s
2018-04-15 12:07:11.9522 [30] Device #5 (CryptoNight): 233.17 h/s
2018-04-15 12:07:12.2179 [28] Device #4 (CryptoNight): 312.91 h/s
2018-04-15 12:07:12.6867 [24] Device #2 (CryptoNight): 313.08 h/s
2018-04-15 12:07:12.9211 [25] Device #3 (CryptoNight): 313.06 h/s
2018-04-15 12:07:14.3900 [26] Device #3 (CryptoNight): 312.76 h/s
2018-04-15 12:07:15.9370 [29] Device #5 (CryptoNight): 233.14 h/s
2018-04-15 12:07:16.9683 [23] Device #2 (CryptoNight): 313.16 h/s
2018-04-15 12:07:17.4996 [15] Device #0 (CryptoNight): 313.66 h/s
2018-04-15 12:07:18.1716 [20] Device #1 (CryptoNight): 204.76 h/s
2018-04-15 12:07:21.8283 [13] Device #0 (CryptoNight): 313.94 h/s
2018-04-15 12:07:22.2501 [27] Device #4 (CryptoNight): 313.18 h/s
2018-04-15 12:07:22.5001 [18] Device #1 (CryptoNight): 204.57 h/s
2018-04-15 12:07:23.4846 [30] Device #5 (CryptoNight): 233.07 h/s
2018-04-15 12:07:23.6722 [28] Device #4 (CryptoNight): 312.86 h/s
2018-04-15 12:07:24.1410 [24] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:07:24.3754 [25] Device #3 (CryptoNight): 312.83 h/s
2018-04-15 12:07:25.8442 [26] Device #3 (CryptoNight): 313.10 h/s
2018-04-15 12:07:27.4694 [29] Device #5 (CryptoNight): 232.93 h/s
2018-04-15 12:07:28.4070 [23] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:07:28.9228 [15] Device #0 (CryptoNight): 313.92 h/s
2018-04-15 12:07:29.1103 [20] Device #1 (CryptoNight): 204.48 h/s
2018-04-15 12:07:30.6572 [12] Received new job: aWTFKKvnCsatry0LcqPyg21MgrmP
2018-04-15 12:07:33.2357 [13] Device #0 (CryptoNight): 314.49 h/s
2018-04-15 12:07:33.4545 [18] Device #1 (CryptoNight): 204.90 h/s
2018-04-15 12:07:33.7045 [27] Device #4 (CryptoNight): 312.84 h/s
2018-04-15 12:07:35.0015 [30] Device #5 (CryptoNight): 233.18 h/s
2018-04-15 12:07:35.1266 [28] Device #4 (CryptoNight): 312.91 h/s
2018-04-15 12:07:35.5954 [24] Device #2 (CryptoNight): 312.84 h/s
2018-04-15 12:07:35.8298 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:07:37.2986 [26] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:07:38.9864 [29] Device #5 (CryptoNight): 233.11 h/s
2018-04-15 12:07:39.8614 [23] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:07:40.0646 [20] Device #1 (CryptoNight): 204.83 h/s
2018-04-15 12:07:40.3459 [15] Device #0 (CryptoNight): 313.76 h/s
2018-04-15 12:07:44.3931 [18] Device #1 (CryptoNight): 205.19 h/s
2018-04-15 12:07:44.6276 [13] Device #0 (CryptoNight): 314.19 h/s
2018-04-15 12:07:45.1589 [27] Device #4 (CryptoNight): 312.83 h/s
2018-04-15 12:07:46.5340 [30] Device #5 (CryptoNight): 233.17 h/s
2018-04-15 12:07:46.5809 [28] Device #4 (CryptoNight): 312.89 h/s
2018-04-15 12:07:47.0497 [24] Device #2 (CryptoNight): 313.08 h/s
2018-04-15 12:07:47.2685 [25] Device #3 (CryptoNight): 313.21 h/s
2018-04-15 12:07:48.7530 [26] Device #3 (CryptoNight): 313.00 h/s
2018-04-15 12:07:50.5188 [29] Device #5 (CryptoNight): 233.10 h/s
2018-04-15 12:07:51.0189 [20] Device #1 (CryptoNight): 204.73 h/s
2018-04-15 12:07:51.3158 [23] Device #2 (CryptoNight): 313.06 h/s
2018-04-15 12:07:51.7533 [15] Device #0 (CryptoNight): 313.93 h/s
2018-04-15 12:07:55.3475 [18] Device #1 (CryptoNight): 205.15 h/s
2018-04-15 12:07:56.0351 [13] Device #0 (CryptoNight): 314.16 h/s
2018-04-15 12:07:56.6132 [27] Device #4 (CryptoNight): 312.95 h/s
2018-04-15 12:07:58.0353 [28] Device #4 (CryptoNight): 313.15 h/s
2018-04-15 12:07:58.0509 [30] Device #5 (CryptoNight): 233.27 h/s
2018-04-15 12:07:58.5040 [24] Device #2 (CryptoNight): 312.56 h/s
2018-04-15 12:07:58.7228 [25] Device #3 (CryptoNight): 313.16 h/s
2018-04-15 12:08:00.1917 [26] Device #3 (CryptoNight): 313.01 h/s
2018-04-15 12:08:01.9576 [20] Device #1 (CryptoNight): 204.93 h/s
2018-04-15 12:08:02.0357 [29] Device #5 (CryptoNight): 233.14 h/s
2018-04-15 12:08:02.7701 [23] Device #2 (CryptoNight): 313.05 h/s
2018-04-15 12:08:03.1608 [15] Device #0 (CryptoNight): 314.58 h/s
2018-04-15 12:08:06.3018 [18] Device #1 (CryptoNight): 204.98 h/s
2018-04-15 12:08:07.4425 [13] Device #0 (CryptoNight): 313.92 h/s
2018-04-15 12:08:08.0520 [27] Device #4 (CryptoNight): 313.27 h/s
2018-04-15 12:08:09.4896 [28] Device #4 (CryptoNight): 312.88 h/s
2018-04-15 12:08:09.5833 [30] Device #5 (CryptoNight): 233.13 h/s
2018-04-15 12:08:09.9584 [24] Device #2 (CryptoNight): 312.96 h/s
2018-04-15 12:08:10.1772 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:08:11.6461 [26] Device #3 (CryptoNight): 313.03 h/s
2018-04-15 12:08:12.9275 [20] Device #1 (CryptoNight): 203.38 h/s
2018-04-15 12:08:13.5681 [29] Device #5 (CryptoNight): 233.12 h/s
2018-04-15 12:08:14.2245 [23] Device #2 (CryptoNight): 312.84 h/s
2018-04-15 12:08:14.5839 [15] Device #0 (CryptoNight): 314.00 h/s
2018-04-15 12:08:17.2873 [18] Device #1 (CryptoNight): 205.16 h/s
2018-04-15 12:08:18.8344 [13] Device #0 (CryptoNight): 315.04 h/s
2018-04-15 12:08:19.5063 [27] Device #4 (CryptoNight): 313.17 h/s
2018-04-15 12:08:20.9440 [28] Device #4 (CryptoNight): 312.95 h/s
2018-04-15 12:08:21.1002 [30] Device #5 (CryptoNight): 233.17 h/s
2018-04-15 12:08:21.3971 [24] Device #2 (CryptoNight): 312.89 h/s
2018-04-15 12:08:21.6159 [25] Device #3 (CryptoNight): 313.16 h/s
2018-04-15 12:08:23.1005 [26] Device #3 (CryptoNight): 312.97 h/s
2018-04-15 12:08:23.8974 [20] Device #1 (CryptoNight): 205.00 h/s
2018-04-15 12:08:25.0850 [29] Device #5 (CryptoNight): 232.98 h/s
2018-04-15 12:08:25.6632 [23] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:08:25.9914 [15] Device #0 (CryptoNight): 314.48 h/s
2018-04-15 12:08:28.2416 [18] Device #1 (CryptoNight): 205.36 h/s
2018-04-15 12:08:30.2419 [13] Device #0 (CryptoNight): 313.93 h/s
2018-04-15 12:08:30.7263 [12] Received new job: uYWWVY7ltnIsow52Hn/yeP4v+p1k
2018-04-15 12:08:30.9450 [27] Device #4 (CryptoNight): 312.83 h/s
2018-04-15 12:08:32.3982 [28] Device #4 (CryptoNight): 312.87 h/s
2018-04-15 12:08:32.6327 [30] Device #5 (CryptoNight): 233.17 h/s
2018-04-15 12:08:32.8515 [24] Device #2 (CryptoNight): 313.15 h/s
2018-04-15 12:08:33.0703 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:08:34.5392 [26] Device #3 (CryptoNight): 312.76 h/s
2018-04-15 12:08:34.8517 [20] Device #1 (CryptoNight): 204.03 h/s
2018-04-15 12:08:36.6175 [29] Device #5 (CryptoNight): 233.07 h/s
2018-04-15 12:08:37.1176 [23] Device #2 (CryptoNight): 312.95 h/s
2018-04-15 12:08:37.3832 [15] Device #0 (CryptoNight): 314.39 h/s
2018-04-15 12:08:39.1958 [18] Device #1 (CryptoNight): 204.69 h/s
2018-04-15 12:08:39.9929 [12] Received new job: jsmgDOPx8rfWIPsgJ38VnSjUWTLC
2018-04-15 12:08:41.6649 [13] Device #0 (CryptoNight): 313.93 h/s
2018-04-15 12:08:42.3993 [27] Device #4 (CryptoNight): 312.94 h/s
2018-04-15 12:08:43.8527 [28] Device #4 (CryptoNight): 312.89 h/s
2018-04-15 12:08:44.1652 [30] Device #5 (CryptoNight): 233.28 h/s
2018-04-15 12:08:44.3059 [24] Device #2 (CryptoNight): 313.11 h/s
2018-04-15 12:08:44.5245 [25] Device #3 (CryptoNight): 312.84 h/s
2018-04-15 12:08:45.8060 [20] Device #1 (CryptoNight): 203.61 h/s
2018-04-15 12:08:45.9935 [26] Device #3 (CryptoNight): 312.99 h/s
2018-04-15 12:08:48.1499 [29] Device #5 (CryptoNight): 233.15 h/s
2018-04-15 12:08:48.5719 [23] Device #2 (CryptoNight): 313.17 h/s
2018-04-15 12:08:48.7906 [15] Device #0 (CryptoNight): 314.39 h/s
2018-04-15 12:08:50.1971 [18] Device #1 (CryptoNight): 201.05 h/s
2018-04-15 12:08:53.0724 [13] Device #0 (CryptoNight): 314.13 h/s
2018-04-15 12:08:53.8538 [27] Device #4 (CryptoNight): 313.16 h/s
2018-04-15 12:08:55.3070 [28] Device #4 (CryptoNight): 312.56 h/s
2018-04-15 12:08:55.6820 [30] Device #5 (CryptoNight): 233.18 h/s
2018-04-15 12:08:55.7602 [24] Device #2 (CryptoNight): 313.05 h/s
2018-04-15 12:08:55.9790 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:08:56.8228 [20] Device #1 (CryptoNight): 204.13 h/s
2018-04-15 12:08:57.4478 [26] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:08:59.3387 [12] Received new job: Hi8/9lxIV70LxkyOIzAEStfd5CJE
2018-04-15 12:08:59.6669 [29] Device #5 (CryptoNight): 233.20 h/s
2018-04-15 12:09:00.0263 [23] Device #2 (CryptoNight): 313.17 h/s
2018-04-15 12:09:00.1981 [15] Device #0 (CryptoNight): 314.19 h/s
2018-04-15 12:09:01.4014 [18] Device #1 (CryptoNight): 185.82 h/s
2018-04-15 12:09:04.4798 [13] Device #0 (CryptoNight): 314.01 h/s
2018-04-15 12:09:05.3080 [27] Device #4 (CryptoNight): 312.73 h/s
2018-04-15 12:09:06.7613 [28] Device #4 (CryptoNight): 312.97 h/s
2018-04-15 12:09:07.2146 [24] Device #2 (CryptoNight): 313.03 h/s
2018-04-15 12:09:07.2146 [30] Device #5 (CryptoNight): 233.37 h/s
2018-04-15 12:09:07.4177 [25] Device #3 (CryptoNight): 312.82 h/s
2018-04-15 12:09:08.0897 [20] Device #1 (CryptoNight): 203.76 h/s
2018-04-15 12:09:08.8866 [26] Device #3 (CryptoNight): 313.39 h/s
2018-04-15 12:09:11.1993 [29] Device #5 (CryptoNight): 233.09 h/s
2018-04-15 12:09:11.4806 [23] Device #2 (CryptoNight): 313.04 h/s
2018-04-15 12:09:11.5900 [15] Device #0 (CryptoNight): 314.68 h/s
2018-04-15 12:09:12.4494 [18] Device #1 (CryptoNight): 204.59 h/s
2018-04-15 12:09:15.9032 [13] Device #0 (CryptoNight): 314.03 h/s
2018-04-15 12:09:16.7624 [27] Device #4 (CryptoNight): 312.94 h/s
2018-04-15 12:09:18.2000 [28] Device #4 (CryptoNight): 313.06 h/s
2018-04-15 12:09:18.6688 [24] Device #2 (CryptoNight): 312.84 h/s
2018-04-15 12:09:18.7313 [30] Device #5 (CryptoNight): 233.20 h/s
2018-04-15 12:09:18.8721 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:09:19.0596 [20] Device #1 (CryptoNight): 204.34 h/s
2018-04-15 12:09:20.3410 [26] Device #3 (CryptoNight): 313.10 h/s
2018-04-15 12:09:22.7162 [29] Device #5 (CryptoNight): 233.04 h/s
2018-04-15 12:09:22.9194 [23] Device #2 (CryptoNight): 313.05 h/s
2018-04-15 12:09:22.9974 [15] Device #0 (CryptoNight): 314.22 h/s
2018-04-15 12:09:23.4037 [18] Device #1 (CryptoNight): 204.11 h/s
2018-04-15 12:09:27.3105 [13] Device #0 (CryptoNight): 313.87 h/s
2018-04-15 12:09:28.2168 [27] Device #4 (CryptoNight): 312.83 h/s
2018-04-15 12:09:29.6545 [28] Device #4 (CryptoNight): 312.84 h/s
2018-04-15 12:09:30.0295 [20] Device #1 (CryptoNight): 201.83 h/s
2018-04-15 12:09:30.1076 [24] Device #2 (CryptoNight): 313.12 h/s
2018-04-15 12:09:30.2638 [30] Device #5 (CryptoNight): 233.14 h/s
2018-04-15 12:09:30.3263 [25] Device #3 (CryptoNight): 313.07 h/s
2018-04-15 12:09:30.8576 [12] Received new job: ZSJ6cBIEgKNh1pJgzBdSFKM8ukj/
2018-04-15 12:09:31.7953 [26] Device #3 (CryptoNight): 312.99 h/s
2018-04-15 12:09:34.2487 [29] Device #5 (CryptoNight): 233.31 h/s
2018-04-15 12:09:34.3737 [23] Device #2 (CryptoNight): 312.94 h/s
2018-04-15 12:09:34.4049 [15] Device #0 (CryptoNight): 314.42 h/s
2018-04-15 12:09:34.4049 [18] Device #1 (CryptoNight): 204.42 h/s
2018-04-15 12:09:38.7179 [13] Device #0 (CryptoNight): 314.26 h/s
2018-04-15 12:09:39.6712 [27] Device #4 (CryptoNight): 312.94 h/s
2018-04-15 12:09:41.0150 [20] Device #1 (CryptoNight): 204.88 h/s
2018-04-15 12:09:41.1088 [28] Device #4 (CryptoNight): 312.91 h/s
2018-04-15 12:09:41.5620 [24] Device #2 (CryptoNight): 313.01 h/s
2018-04-15 12:09:41.7651 [25] Device #3 (CryptoNight): 313.05 h/s
2018-04-15 12:09:41.7964 [30] Device #5 (CryptoNight): 233.24 h/s
2018-04-15 12:09:43.2497 [26] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:09:45.3604 [18] Device #1 (CryptoNight): 204.97 h/s
2018-04-15 12:09:45.7667 [29] Device #5 (CryptoNight): 233.07 h/s
2018-04-15 12:09:45.8136 [15] Device #0 (CryptoNight): 313.91 h/s
2018-04-15 12:09:45.8292 [23] Device #2 (CryptoNight): 313.05 h/s
2018-04-15 12:09:50.1265 [13] Device #0 (CryptoNight): 314.05 h/s
2018-04-15 12:09:51.1267 [27] Device #4 (CryptoNight): 313.17 h/s
2018-04-15 12:09:52.0174 [20] Device #1 (CryptoNight): 204.69 h/s
2018-04-15 12:09:52.5643 [28] Device #4 (CryptoNight): 312.84 h/s
2018-04-15 12:09:53.0175 [24] Device #2 (CryptoNight): 313.16 h/s
2018-04-15 12:09:53.2206 [25] Device #3 (CryptoNight): 312.94 h/s
2018-04-15 12:09:53.3144 [30] Device #5 (CryptoNight): 233.12 h/s
2018-04-15 12:09:54.6895 [26] Device #3 (CryptoNight): 312.98 h/s
2018-04-15 12:09:56.3616 [18] Device #1 (CryptoNight): 205.07 h/s
2018-04-15 12:09:57.2054 [15] Device #0 (CryptoNight): 314.06 h/s
2018-04-15 12:09:57.2836 [23] Device #2 (CryptoNight): 313.06 h/s
2018-04-15 12:09:57.3004 [29] Device #5 (CryptoNight): 233.15 h/s
2018-04-15 12:09:59.2056 [1] Stopping miners...
2018-04-15 12:10:01.2370 [1] Stopped miners.
/code]
I agree, the Sqlite is really slow. Unless you can't speed it up, i'd prefer something easier as well.
My opinion on the card settings:
- Radeon 550, the Baffin is slower on GGS than on xmr-stak. About 8-10%, Where xmr-stak gives a steady 560 H/s @1150/1950, GGS is jumping between 510 and 540. Maybe the algo needs a closer look.
- Memory timings: I posted a elpida strap for cryptonight, before, did someone use it? I managed to squeeze a bit more out of it for the bad memory cards, giving now 920h/s with 1150/1750.
As soon i good some free time i will check the memory timings and hand them over...GGS deserves this support, really.
Maybe this helps.
My opinion on the card settings:
- Radeon 550, the Baffin is slower on GGS than on xmr-stak. About 8-10%, Where xmr-stak gives a steady 560 H/s @1150/1950, GGS is jumping between 510 and 540. Maybe the algo needs a closer look.
- Memory timings: I posted a elpida strap for cryptonight, before, did someone use it? I managed to squeeze a bit more out of it for the bad memory cards, giving now 920h/s with 1150/1750.
As soon i good some free time i will check the memory timings and hand them over...GGS deserves this support, really.
Maybe this helps.
That'd be a huge help. Thanks a lot!
As fo RX 580, the default value for intensity must be off. Please let me know if you come up with a good value.
I like your miner, a lot of personalization.
I have only one gpu for now, RX 580 8 GB hynix memory without bios mod.
If use your memory timing it freez my pc.
I use cryptonight 7 and custom pool.
Good project, thank you.
Due to long loading time and long starting without binaries, returning to 1.3.2 version...
Every launch in log writes:
2018-04-15 20:32:35.5210 [1] Failed to initialize NVIDIA Management Library.
2018-04-15 20:32:35.5380 [1] Exception in UpdateControls(): The given key was not present in the dictionary. at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at GatelessGateSharp.MainForm.UpdateControls()
Every launch in log writes:
2018-04-15 20:32:35.5210 [1] Failed to initialize NVIDIA Management Library.
2018-04-15 20:32:35.5380 [1] Exception in UpdateControls(): The given key was not present in the dictionary. at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at GatelessGateSharp.MainForm.UpdateControls()
I agree, the Sqlite is really slow. Unless you can't speed it up, i'd prefer something easier as well.
My opinion on the card settings:
- Radeon 550, the Baffin is slower on GGS than on xmr-stak. About 8-10%, Where xmr-stak gives a steady 560 H/s @1150/1950, GGS is jumping between 510 and 540. Maybe the algo needs a closer look.
- Memory timings: I posted a elpida strap for cryptonight, before, did someone use it? I managed to squeeze a bit more out of it for the bad memory cards, giving now 920h/s with 1150/1750.
As soon i good some free time i will check the memory timings and hand them over...GGS deserves this support, really.
Maybe this helps.
My opinion on the card settings:
- Radeon 550, the Baffin is slower on GGS than on xmr-stak. About 8-10%, Where xmr-stak gives a steady 560 H/s @1150/1950, GGS is jumping between 510 and 540. Maybe the algo needs a closer look.
- Memory timings: I posted a elpida strap for cryptonight, before, did someone use it? I managed to squeeze a bit more out of it for the bad memory cards, giving now 920h/s with 1150/1750.
As soon i good some free time i will check the memory timings and hand them over...GGS deserves this support, really.
Maybe this helps.
That'd be a huge help. Thanks a lot!
As fo RX 580, the default value for intensity must be off. Please let me know if you come up with a good value.
Optimization when passed local work size and must do intensity tests gives error and restarts.
Thanks for parsing timings from string. I make applaying timings from my bios mod. With that mod GGS works stable. But when I apply them in GGS and check "Enable" GGS give system hang with BSOD THREAD_STUCK_IN_DEVICE_DRIVER
Rebuilding bins for cryptonight also didn't work. Error appears that GGS can't save bin this incorrect name.
And you must make possibility to not close RadeonSettings. Make an option for this. Like "Disable autounloading RadeonSettings from memory"
Please rerurn possibiity to use bins for cryptonight. And it's need to add possibility to mine each GPU they own algo.
Thanks for parsing timings from string. I make applaying timings from my bios mod. With that mod GGS works stable. But when I apply them in GGS and check "Enable" GGS give system hang with BSOD THREAD_STUCK_IN_DEVICE_DRIVER
Rebuilding bins for cryptonight also didn't work. Error appears that GGS can't save bin this incorrect name.
And you must make possibility to not close RadeonSettings. Make an option for this. Like "Disable autounloading RadeonSettings from memory"
Please rerurn possibiity to use bins for cryptonight. And it's need to add possibility to mine each GPU they own algo.
Ok, it doesn't work in one part:
x16R
Two biggest pool are suprnova ( but I can't as its similar to mining pool hub require registration) and ravenminer. I use zergpool for test normally but noone of the 3 work.
Basically the non default pool doesn't work even if selected. I will test for other algos
I (GGS, not me as I didn't know they exist) connected now to cryptopoolparty and speed seem ok but better than whatever I achieved with sgminer going over 7.3 Mh/s for each rx 580 so this part is working. Problem is that GGS isn't taking an average of the speed (all the algos are changing)so I can only wait for the pool to recognize me and I don't know how to deal with that and making test on the various options.
For now I will wait result from the pool.
Edit:
no, all the custom pool doesn't work.
Kindly note that
Cryptonight lite is not cryptonight lite v7 that is what is supported right now from turtlecoin and will be from aeon later on. the non v7 will be alive for another 24h and then death. So, what's the point ?
x16R
Two biggest pool are suprnova ( but I can't as its similar to mining pool hub require registration) and ravenminer. I use zergpool for test normally but noone of the 3 work.
Basically the non default pool doesn't work even if selected. I will test for other algos
I (GGS, not me as I didn't know they exist) connected now to cryptopoolparty and speed seem ok but better than whatever I achieved with sgminer going over 7.3 Mh/s for each rx 580
so this part is working. Problem is that GGS isn't taking an average of the speed (all the algos are changing)so I can only wait for the pool to recognize me and I don't know how to deal with that and making test on the various options.For now I will wait result from the pool.
Edit:
no, all the custom pool doesn't work.
Kindly note that
Cryptonight lite is not cryptonight lite v7 that is what is supported right now from turtlecoin and will be from aeon later on. the non v7 will be alive for another 24h and then death. So, what's the point ?
Did you choose "Custom Pools" for "Default Pool"?
GGS 1.3.3
1. zawawa, you removed cryptonoght bins. Why? Loading cryptonight now in times longer...
2. Default Intensity for v7 is 131
But 128 is better for RX 580...
3. And you wanted to make conversation memory timings from string...
4. Minimum fan speed is 20%. Need 0.
5. Radeon Settings didn't work if GGS launched.
6. What's means new parameters: Strided index and Memory chunk size?
7. On my 2nd RX 580 Nitro+ memory is shows as Hynix (that's right), but on 1st RX 580 from MSI memory type not showed at all (Hynix too must show).
8. Enabling GGS overclock still leads to high CPU usage - about 8-11% on 8 core CPU. Without OC GGS use normal 1-2%.
9. Visual bug: words "Hynix GDDR5" is lower in string than words in rows left and right from it. Looks like bottom alignment insteed of center alignment.
10. Cryptonight V7 with Intensity 128 now uses only 4Gb videomemory. In 1.2.8 it uses 4.3Gb videomemory llike original CN. You optimized kernels or it's a calculate bug?
1. zawawa, you removed cryptonoght bins. Why? Loading cryptonight now in times longer...
2. Default Intensity for v7 is 131
But 128 is better for RX 580...3. And you wanted to make conversation memory timings from string...
4. Minimum fan speed is 20%. Need 0.
5. Radeon Settings didn't work if GGS launched.
6. What's means new parameters: Strided index and Memory chunk size?
7. On my 2nd RX 580 Nitro+ memory is shows as Hynix (that's right), but on 1st RX 580 from MSI memory type not showed at all (Hynix too must show).
8. Enabling GGS overclock still leads to high CPU usage - about 8-11% on 8 core CPU. Without OC GGS use normal 1-2%.
9. Visual bug: words "Hynix GDDR5" is lower in string than words in rows left and right from it. Looks like bottom alignment insteed of center alignment.
10. Cryptonight V7 with Intensity 128 now uses only 4Gb videomemory. In 1.2.8 it uses 4.3Gb videomemory llike original CN. You optimized kernels or it's a calculate bug?
1. I had to remove it for additional parameters.
2. Optimize device settings for RX 580, click "Save to File," and email the saved file to me.
3. Click "Apply Strap."
4. I will fix that.
5. Radeon Settings is not compatible with GGS.
6. They are adopted from XMR Stak.
7. You need to enable PhyMem.
8. I will adjust parameters.
9. I will fix that.
10. There was a bug.
5. What about this issue:https://github.com/zawawawa/GatelessGateSharp/issues/67
10. Does a bug means that V7 uses less memory than orig CN? Or bug was in 4.3Gb on origCN?
2. For optimize does it safe to use timings for Hynix memory?
GGS 1.3.3
1. zawawa, you removed cryptonoght bins. Why? Loading cryptonight now in times longer...
2. Default Intensity for v7 is 131 But 128 is better for RX 580...
3. And you wanted to make conversation memory timings from string...
4. Minimum fan speed is 20%. Need 0.
5. Radeon Settings didn't work if GGS launched.
6. What's means new parameters: Strided index and Memory chunk size?
7. On my 2nd RX 580 Nitro+ memory is shows as Hynix (that's right), but on 1st RX 580 from MSI memory type not showed at all (Hynix too must show).
8. Enabling GGS overclock still leads to high CPU usage - about 8-11% on 8 core CPU. Without OC GGS use normal 1-2%.
9. Visual bug: words "Hynix GDDR5" is lower in string than words in rows left and right from it. Looks like bottom alignment insteed of center alignment.
10. Cryptonight V7 with Intensity 128 now uses only 4Gb videomemory. In 1.2.8 it uses 4.3Gb videomemory llike original CN. You optimized kernels or it's a calculate bug?
1. zawawa, you removed cryptonoght bins. Why? Loading cryptonight now in times longer...
2. Default Intensity for v7 is 131
But 128 is better for RX 580...3. And you wanted to make conversation memory timings from string...
4. Minimum fan speed is 20%. Need 0.
5. Radeon Settings didn't work if GGS launched.
6. What's means new parameters: Strided index and Memory chunk size?
7. On my 2nd RX 580 Nitro+ memory is shows as Hynix (that's right), but on 1st RX 580 from MSI memory type not showed at all (Hynix too must show).
8. Enabling GGS overclock still leads to high CPU usage - about 8-11% on 8 core CPU. Without OC GGS use normal 1-2%.
9. Visual bug: words "Hynix GDDR5" is lower in string than words in rows left and right from it. Looks like bottom alignment insteed of center alignment.
10. Cryptonight V7 with Intensity 128 now uses only 4Gb videomemory. In 1.2.8 it uses 4.3Gb videomemory llike original CN. You optimized kernels or it's a calculate bug?
1. I had to remove it for additional parameters.
2. Optimize device settings for RX 580, click "Save to File," and email the saved file to me.
3. Click "Apply Strap."
4. I will fix that.
5. Radeon Settings is not compatible with GGS.
6. They are adopted from XMR Stak.
7. You need to enable PhyMem.
8. I will adjust parameters.
9. I will fix that.
10. There was a bug.
GGS 1.3.3
1. zawawa, you removed cryptonoght bins. Why? Loading cryptonight now in times longer...
2. Default Intensity for v7 is 131 But 128 is better for RX 580...
3. And you wanted to make conversation memory timings from string...
4. Minimum fan speed is 20%. Need 0.
5. Radeon Settings didn't work if GGS launched.
6. What's means new parameters: Strided index and Memory chunk size?
7. On my 2nd RX 580 Nitro+ memory is shows as Hynix (that's right), but on 1st RX 580 from MSI memory type not showed at all (Hynix too must show).
8. Enabling GGS overclock still leads to high CPU usage - about 8-11% on 8 core CPU. Without OC GGS use normal 1-2%.
9. Visual bug: words "Hynix GDDR5" is lower in string than words in rows left and right from it. Looks like bottom alignment insteed of center alignment.
10. Cryptonight V7 with Intensity 128 now uses only 4Gb videomemory. In 1.2.8 it uses 4.3Gb videomemory llike original CN. You optimized kernels or it's a calculate bug?
11. Very long loading GGS. IMHO, longer than 1.3.2... Including long cryptonight loading due to absent of bins. Now starting mining is too long.
1. zawawa, you removed cryptonoght bins. Why? Loading cryptonight now in times longer...
2. Default Intensity for v7 is 131
But 128 is better for RX 580...3. And you wanted to make conversation memory timings from string...
4. Minimum fan speed is 20%. Need 0.
5. Radeon Settings didn't work if GGS launched.
6. What's means new parameters: Strided index and Memory chunk size?
7. On my 2nd RX 580 Nitro+ memory is shows as Hynix (that's right), but on 1st RX 580 from MSI memory type not showed at all (Hynix too must show).
8. Enabling GGS overclock still leads to high CPU usage - about 8-11% on 8 core CPU. Without OC GGS use normal 1-2%.
9. Visual bug: words "Hynix GDDR5" is lower in string than words in rows left and right from it. Looks like bottom alignment insteed of center alignment.
10. Cryptonight V7 with Intensity 128 now uses only 4Gb videomemory. In 1.2.8 it uses 4.3Gb videomemory llike original CN. You optimized kernels or it's a calculate bug?
11. Very long loading GGS. IMHO, longer than 1.3.2... Including long cryptonight loading due to absent of bins. Now starting mining is too long.
Any chance to sort the GPUs in the same order number as OverdriveNtool does?
Maybe something for the next release.
Maybe something for the next release.
When will the version for Linux?
X16 bins have to much size... It's need to do something this them...
There are three sets for three local work sizes: 64, 128, and 256.
I should probably keep 64 only.
X16 bins have to much size... It's need to do something this them...
Gateless Gate Sharp 1.3.3 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.3-alpha
* Added full support for CryptoNightV7, CryptoNight-Heavy, CryptoNight-Light, X16R, and X16S.
* Added support for Raven, Pigeoncoin, Sumokoin, and AEON.
* Added new default pools including Mining Pool Hub.
* Updated default device settings.
* Improved device settings handling, benchmarking, and optimization.
* Numerous bug fixes and improvements.
Hope this version is worth the wait. Enjoy!
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.3-alpha
* Added full support for CryptoNightV7, CryptoNight-Heavy, CryptoNight-Light, X16R, and X16S.
* Added support for Raven, Pigeoncoin, Sumokoin, and AEON.
* Added new default pools including Mining Pool Hub.
* Updated default device settings.
* Improved device settings handling, benchmarking, and optimization.
* Numerous bug fixes and improvements.
Hope this version is worth the wait. Enjoy!
Just tried your software for the first time. It seems quite good, like the gui (as opposed to a dos command window) but:
For users who don't have direct access to their rigs and rely on remote desktop apps, your gui doesn't scale at all, most of the boxes are outside the visible range.
Now, you could possibly force the text size to display smaller, and even run it in some compatibility mode, but unfortunately that's too much trial and error. I would recommend you simplify the gui and make it less "busy".
Just my two cents...
Ok, it doesn't work in one part:
x16R
Two biggest pool are suprnova ( but I can't as its similar to mining pool hub require registration) and ravenminer. I use zergpool for test normally but noone of the 3 work.
Basically the non default pool doesn't work even if selected. I will test for other algos
I (GGS, not me as I didn't know they exist) connected now to cryptopoolparty and speed seem ok but better than whatever I achieved with sgminer going over 7.3 Mh/s for each rx 580 so this part is working. Problem is that GGS isn't taking an average of the speed (all the algos are changing)so I can only wait for the pool to recognize me and I don't know how to deal with that and making test on the various options.
For now I will wait result from the pool.
Edit:
no, all the custom pool doesn't work.
Kindly note that
Cryptonight lite is not cryptonight lite v7 that is what is supported right now from turtlecoin and will be from aeon later on. the non v7 will be alive for another 24h and then death. So, what's the point ?
.
x16R
Two biggest pool are suprnova ( but I can't as its similar to mining pool hub require registration) and ravenminer. I use zergpool for test normally but noone of the 3 work.
Basically the non default pool doesn't work even if selected. I will test for other algos
I (GGS, not me as I didn't know they exist) connected now to cryptopoolparty and speed seem ok but better than whatever I achieved with sgminer going over 7.3 Mh/s for each rx 580
so this part is working. Problem is that GGS isn't taking an average of the speed (all the algos are changing)so I can only wait for the pool to recognize me and I don't know how to deal with that and making test on the various options.For now I will wait result from the pool.
Edit:
no, all the custom pool doesn't work.
Kindly note that
Cryptonight lite is not cryptonight lite v7 that is what is supported right now from turtlecoin and will be from aeon later on. the non v7 will be alive for another 24h and then death. So, what's the point ?
.
Jump to: