Topic: Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480! - page 65. (Read 214431 times)
To reproduce high CPU usage and instability issues, use any pool, just disconnect internet and reconnect after some seconds or minutes, when come back, comes with many issues. Never auto recover. Only relaunching to resolve the problem.
zawawa, please comment on
you wrote the software, so you know how it really work.
I can test various worksize /intensity setting, but a guidelines just to understand the direction, can be really useful
For some of you who are getting low hast rates, I would suggest experimenting threads, Intensity, and Worksize. I have an older card I have been experimenting with. I have noticed a different versions of GGS with have different hashrate with the same settings, but changing the setting I can still maximize the hashrate.
So far the best results (for my card) follow a pattern:
1. A single thread
2. Intensity in multiples of twice the compute units
3. Intensity set to use half of the video cards memory. This will smooth out the hashrate
4. WorkSize set to 128.
Code:
AMD 17.12.2 GGS 1.2.12 alpha Nicehash Neoscrypt
T = 1 I = 64 WorkSize = 64 Mem: 346/2048 160 KH/s
T = 1 I = 64 WorkSize = 128 Mem: 471/2048 220 KH/s
T = 1 I = 70 WorkSize = 128 Mem: 530/2048 232 KH/s
T = 1 I = 84 WorkSize = 128 Mem: 586/2048 292 KH/s
T = 1 I = 112 WorkSize = 128 Mem: 697/2048 294 KH/s
T = 1 I = 224 WorkSize = 128 Mem: 1147/2048 296 KH/s
T = 1 I = 224 WorkSize = 192 Mem: 1596/2048 230 KH/s
T = 1 I = 224 WorkSize = 254 Mem: 1664/2048 104 KH/s
T = 1 I = 64 WorkSize = 64 Mem: 346/2048 160 KH/s
T = 1 I = 64 WorkSize = 128 Mem: 471/2048 220 KH/s
T = 1 I = 70 WorkSize = 128 Mem: 530/2048 232 KH/s
T = 1 I = 84 WorkSize = 128 Mem: 586/2048 292 KH/s
T = 1 I = 112 WorkSize = 128 Mem: 697/2048 294 KH/s
T = 1 I = 224 WorkSize = 128 Mem: 1147/2048 296 KH/s
T = 1 I = 224 WorkSize = 192 Mem: 1596/2048 230 KH/s
T = 1 I = 224 WorkSize = 254 Mem: 1664/2048 104 KH/s
So far the best results (for my card) follow a pattern:
1. A single thread
2. Intensity in multiples of twice the compute units
3. Intensity set to use half of the video cards memory. This will smooth out the hashrate
4. WorkSize set to 128.
you wrote the software, so you know how it really work.
I can test various worksize /intensity setting, but a guidelines just to understand the direction, can be really useful
Well, I would love see you guys and gals to collect more data to figure out underlying patterns.
We can speculate about possible best values for these parameters, but, ultimately, we need to try them out to see if they actually work.
I will eventually implement a feature to automate such fine-tuning.
jperser's suggestions do sound reasonable to me, but I won't draw any conclusions yet before I test them myself. Technically speaking, WORKSIZE=64 is a natural starting point because that is the size of the wavefront for GCN and thus allows the driver to eliminate certain instructions for wavefront synchronizations. That benefit may be outweighed with WORKSIZE=128, 192, or 256, however, by having multiple wavefronts on the same compute unit to hide latency in slow memory access.
Zawawa, if you really have the time for a new algo, where some real devfee can be made, think about equilhash, as there isn't a nice solution for AMD.
On the opposite, neoscrypt for linux can be a good choice
On the opposite, neoscrypt for linux can be a good choice
+++
That would be great. Somewhere saw a post that Gateless Gate miner will be added soon to the niveos. Is it true that you are going to do this? and when it will be approximately?
zawawa, please comment on
you wrote the software, so you know how it really work.
I can test various worksize /intensity setting, but a guidelines just to understand the direction, can be really useful
For some of you who are getting low hast rates, I would suggest experimenting threads, Intensity, and Worksize. I have an older card I have been experimenting with. I have noticed a different versions of GGS with have different hashrate with the same settings, but changing the setting I can still maximize the hashrate.
So far the best results (for my card) follow a pattern:
1. A single thread
2. Intensity in multiples of twice the compute units
3. Intensity set to use half of the video cards memory. This will smooth out the hashrate
4. WorkSize set to 128.
Code:
AMD 17.12.2 GGS 1.2.12 alpha Nicehash Neoscrypt
T = 1 I = 64 WorkSize = 64 Mem: 346/2048 160 KH/s
T = 1 I = 64 WorkSize = 128 Mem: 471/2048 220 KH/s
T = 1 I = 70 WorkSize = 128 Mem: 530/2048 232 KH/s
T = 1 I = 84 WorkSize = 128 Mem: 586/2048 292 KH/s
T = 1 I = 112 WorkSize = 128 Mem: 697/2048 294 KH/s
T = 1 I = 224 WorkSize = 128 Mem: 1147/2048 296 KH/s
T = 1 I = 224 WorkSize = 192 Mem: 1596/2048 230 KH/s
T = 1 I = 224 WorkSize = 254 Mem: 1664/2048 104 KH/s
So far the best results (for my card) follow a pattern:
1. A single thread
2. Intensity in multiples of twice the compute units
3. Intensity set to use half of the video cards memory. This will smooth out the hashrate
4. WorkSize set to 128.
you wrote the software, so you know how it really work.
I can test various worksize /intensity setting, but a guidelines just to understand the direction, can be really useful
I figure out why GGS start to use CPU after large amount of time running with jumps from 0-1 to 14-15%.
It's due to updating log.
After clearing the log on log tab CPU usage drops to 0-2% like at GGS launch.
zawawa, you must do something this that. Maybe make limit of strings on the log tab? Because amout of that strings grows with time...
It's due to updating log.
After clearing the log on log tab CPU usage drops to 0-2% like at GGS launch.
zawawa, you must do something this that. Maybe make limit of strings on the log tab? Because amout of that strings grows with time...
The amount of the text on the log tab is already limited. I think there is a bug in the library that causes memory leaks.
Thanks for the nice catch!
For some of you who are getting low hast rates, I would suggest experimenting threads, Intensity, and Worksize. I have an older card I have been experimenting with. I have noticed a different versions of GGS with have different hashrate with the same settings, but changing the setting I can still maximize the hashrate.
So far the best results (for my card) follow a pattern:
1. A single thread
2. Intensity in multiples of twice the compute units
3. Intensity set to use half of the video cards memory. This will smooth out the hashrate
4. WorkSize set to 128.
Where is results for next variants:Code:
AMD 17.12.2 GGS 1.2.12 alpha Nicehash Neoscrypt
T = 1 I = 64 WorkSize = 64 Mem: 346/2048 160 KH/s
T = 1 I = 64 WorkSize = 128 Mem: 471/2048 220 KH/s
T = 1 I = 70 WorkSize = 128 Mem: 530/2048 232 KH/s
T = 1 I = 84 WorkSize = 128 Mem: 586/2048 292 KH/s
T = 1 I = 112 WorkSize = 128 Mem: 697/2048 294 KH/s
T = 1 I = 224 WorkSize = 128 Mem: 1147/2048 296 KH/s
T = 1 I = 224 WorkSize = 192 Mem: 1596/2048 230 KH/s
T = 1 I = 224 WorkSize = 254 Mem: 1664/2048 104 KH/s
So far the best results (for my card) follow a pattern:
1. A single thread
2. Intensity in multiples of twice the compute units
3. Intensity set to use half of the video cards memory. This will smooth out the hashrate
4. WorkSize set to 128.
I=128 W=64
I=256 W=64
I=160 W=64
I=64 W=192
I=128 W=192
I=64 W=256
etc.
With W=64 you did too small amount of tests. Same as with W=192 and W=256
Don't try to set W to numbers that didn't devide to 8. Intensity is also best when set to numbers deviding to 8.
For some of you who are getting low hast rates, I would suggest experimenting threads, Intensity, and Worksize. I have an older card I have been experimenting with. I have noticed a different versions of GGS with have different hashrate with the same settings, but changing the setting I can still maximize the hashrate.
So far the best results (for my card) follow a pattern:
1. A single thread
2. Intensity in multiples of twice the compute units
3. Intensity set to use half of the video cards memory. This will smooth out the hashrate
4. WorkSize set to 128.
Code:
AMD 17.12.2 GGS 1.2.12 alpha Nicehash Neoscrypt
T = 1 I = 64 WorkSize = 64 Mem: 346/2048 160 KH/s
T = 1 I = 64 WorkSize = 128 Mem: 471/2048 220 KH/s
T = 1 I = 70 WorkSize = 128 Mem: 530/2048 232 KH/s
T = 1 I = 84 WorkSize = 128 Mem: 586/2048 292 KH/s
T = 1 I = 112 WorkSize = 128 Mem: 697/2048 294 KH/s
T = 1 I = 224 WorkSize = 128 Mem: 1147/2048 296 KH/s
T = 1 I = 224 WorkSize = 192 Mem: 1596/2048 230 KH/s
T = 1 I = 224 WorkSize = 254 Mem: 1664/2048 104 KH/s
So far the best results (for my card) follow a pattern:
1. A single thread
2. Intensity in multiples of twice the compute units
3. Intensity set to use half of the video cards memory. This will smooth out the hashrate
4. WorkSize set to 128.
The screen scaling problems still under 4k. Try different dpi sizes to reproduce!
https://www.imageupload.co.uk/images/2018/01/30/4kProblems.png
https://www.imageupload.co.uk/images/2018/01/30/4kProblems.png
Scaling works perfectly fine with Windows 10 Creators Update. Which operating system are you using?
Windows 10 last version. Using terminal mstsc in different versions. Scaling not works perfectly fine. If you want, I can get more details about resolution and DPI fonts
Zawawa, if you really have the time for a new algo, where some real devfee can be made, think about equilhash, as there isn't a nice solution for AMD.
On the opposite, neoscrypt for linux can be a good choice
On the opposite, neoscrypt for linux can be a good choice
hi,@zawawa!!! plz realise algo !!!!tribus xevan!!!!! on miner))
hi
retest the last version ,still drop 100-150h/per 570 on cryptonight.maube i must try the adrenalin driver and not the blockchain?
it start well ,850/870h but few minutes later 750h :/ and still stable to it :/
in pool custom ,when i put a worker name after my wallet ,like that wallet.rig1,ggs can't start mining,it tell he cant find the pool.work great without .rig1
retest the last version ,still drop 100-150h/per 570 on cryptonight.maube i must try the adrenalin driver and not the blockchain?
it start well ,850/870h but few minutes later 750h :/ and still stable to it :/
in pool custom ,when i put a worker name after my wallet ,like that wallet.rig1,ggs can't start mining,it tell he cant find the pool.work great without .rig1
Thank you for your hardwork zawawa, bes neoscrypt miner for AMD. i will update results if I have any problem.
My configuration;
Win10 64x Pro
6x Sapphire Nitro+ Rx580
Celeron G4400 CPU
Radeon Adrenaline 17.12.2 Driver
Custom bsod pool
https://image.ibb.co/eHAMZR/zawawa.jpg
Edit 1: First switching to devfee was succesful.
My configuration;
Win10 64x Pro
6x Sapphire Nitro+ Rx580
Celeron G4400 CPU
Radeon Adrenaline 17.12.2 Driver
Custom bsod pool
https://image.ibb.co/eHAMZR/zawawa.jpg
Edit 1: First switching to devfee was succesful.
The screen scaling problems still under 4k. Try different dpi sizes to reproduce!
Scaling works perfectly fine with Windows 10 Creators Update. Which operating system are you using?
Alright, when you guys report connection problems with custom pools, I need to know the following:
(1) the host,
(2) the coin you are mining,
(3) the algorithm, and
(4) your graphics cards.
I really wish GGS would be useful for you, but you just cannot expect GGS to be compatible with all the pools out there in the wild straight out of the box, and my crystal ball is totally abused lately. Thanks!
(1) the host,
(2) the coin you are mining,
(3) the algorithm, and
(4) your graphics cards.
I really wish GGS would be useful for you, but you just cannot expect GGS to be compatible with all the pools out there in the wild straight out of the box, and my crystal ball is totally abused lately. Thanks!
2018-01-30 16:26:43.4651 [1] Saved settings.
2018-01-30 16:26:43.4776 [1] Saving settings to C:\Users\user\AppData\Roaming\GatelessGateSharp\Backups\2018-01-30--1626.sqlite...
2018-01-30 16:26:45.4514 [1] Saved settings.
2018-01-30 16:26:45.4915 [1] Launching miner(s) for Custom Pool 0...
2018-01-30 16:26:45.4920 [7] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:26:45.4925 [7] Reconnecting to the server...
2018-01-30 16:26:45.5155 [17] Miner thread for Device #0 started.
2018-01-30 16:26:45.5155 [17] NiceHash mode is off.
2018-01-30 16:26:45.5190 [17] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #0.
2018-01-30 16:26:45.5335 [17] Built cryptonight program for Device #0.
2018-01-30 16:26:45.5335 [17] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:45.6648 [16] Miner thread for Device #0 started.
2018-01-30 16:26:45.6648 [16] NiceHash mode is off.
2018-01-30 16:26:45.6678 [16] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #0.
2018-01-30 16:26:45.6748 [16] Built cryptonight program for Device #0.
2018-01-30 16:26:45.6748 [16] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:45.8134 [18] Miner thread for Device #1 started.
2018-01-30 16:26:45.8134 [18] NiceHash mode is off.
2018-01-30 16:26:45.8154 [18] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #1.
2018-01-30 16:26:45.8332 [18] Built cryptonight program for Device #1.
2018-01-30 16:26:45.8332 [18] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:45.9535 [8] Miner thread for Device #1 started.
2018-01-30 16:26:45.9535 [8] NiceHash mode is off.
2018-01-30 16:26:45.9570 [8] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #1.
2018-01-30 16:26:45.9744 [8] Built cryptonight program for Device #1.
2018-01-30 16:26:45.9744 [8] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:46.0983 [9] Miner thread for Device #2 started.
2018-01-30 16:26:46.0983 [9] NiceHash mode is off.
2018-01-30 16:26:46.1074 [9] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #2.
2018-01-30 16:26:46.1169 [9] Built cryptonight program for Device #2.
2018-01-30 16:26:46.1169 [9] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:46.2391 [10] Miner thread for Device #2 started.
2018-01-30 16:26:46.2391 [10] NiceHash mode is off.
2018-01-30 16:26:46.2416 [10] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #2.
2018-01-30 16:26:46.2496 [10] Built cryptonight program for Device #2.
2018-01-30 16:26:46.2496 [10] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:46.3927 [12] Miner thread for Device #3 started.
2018-01-30 16:26:46.3927 [12] NiceHash mode is off.
2018-01-30 16:26:46.4077 [12] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #3.
2018-01-30 16:26:46.4639 [12] Built cryptonight program for Device #3.
2018-01-30 16:26:46.4639 [12] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:46.5409 [13] Miner thread for Device #3 started.
2018-01-30 16:26:46.5409 [13] NiceHash mode is off.
2018-01-30 16:26:46.5444 [13] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #3.
2018-01-30 16:26:46.5519 [13] Built cryptonight program for Device #3.
2018-01-30 16:26:46.5519 [13] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:50.4927 [7] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:26:50.4932 [7] Reconnecting to the server...
2018-01-30 16:26:55.4936 [7] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:26:55.4941 [7] Reconnecting to the server...
2018-01-30 16:27:00.4952 [7] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:27:00.7109 [1] Stopping miners...
2018-01-30 16:27:00.7186 [8] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7201 [16] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7566 [9] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7756 [18] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7801 [17] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7891 [10] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7916 [13] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.8101 [12] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.9398 [1] Stopped miners.
2018-01-30 16:27:00.9503 [1] Stopping miners...
2018-01-30 16:27:00.9893 [1] Stopped miners.
2018-01-30 16:27:01.0053 [1] Launching miner(s) for Custom Pool 0...
2018-01-30 16:27:01.0063 [13] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:27:01.0063 [13] Reconnecting to the server...
2018-01-30 16:27:01.0304 [12] Miner thread for Device #0 started.
2018-01-30 16:27:01.0309 [12] NiceHash mode is off.
2018-01-30 16:27:01.0349 [12] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #0.
2018-01-30 16:27:01.0429 [12] Built cryptonight program for Device #0.
2018-01-30 16:27:01.0429 [12] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.1982 [10] Miner thread for Device #0 started.
2018-01-30 16:27:01.1982 [10] NiceHash mode is off.
2018-01-30 16:27:01.2012 [10] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #0.
2018-01-30 16:27:01.2097 [10] Built cryptonight program for Device #0.
2018-01-30 16:27:01.2097 [10] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.3533 [9] Miner thread for Device #1 started.
2018-01-30 16:27:01.3533 [9] NiceHash mode is off.
2018-01-30 16:27:01.3564 [9] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #1.
2018-01-30 16:27:01.3674 [9] Built cryptonight program for Device #1.
2018-01-30 16:27:01.3674 [9] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.5071 [8] Miner thread for Device #1 started.
2018-01-30 16:27:01.5071 [8] NiceHash mode is off.
2018-01-30 16:27:01.5100 [8] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #1.
2018-01-30 16:27:01.5181 [8] Built cryptonight program for Device #1.
2018-01-30 16:27:01.5181 [8] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.6594 [18] Miner thread for Device #2 started.
2018-01-30 16:27:01.6594 [18] NiceHash mode is off.
2018-01-30 16:27:01.6624 [18] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #2.
2018-01-30 16:27:01.6815 [18] Built cryptonight program for Device #2.
2018-01-30 16:27:01.6820 [18] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.8110 [16] Miner thread for Device #2 started.
2018-01-30 16:27:01.8110 [16] NiceHash mode is off.
2018-01-30 16:27:01.8141 [16] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #2.
2018-01-30 16:27:01.8375 [16] Built cryptonight program for Device #2.
2018-01-30 16:27:01.8375 [16] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.9911 [17] Miner thread for Device #3 started.
2018-01-30 16:27:01.9911 [17] NiceHash mode is off.
2018-01-30 16:27:01.9946 [17] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #3.
2018-01-30 16:27:02.0021 [17] Built cryptonight program for Device #3.
2018-01-30 16:27:02.0026 [17] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:02.1376 [7] Miner thread for Device #3 started.
2018-01-30 16:27:02.1376 [7] NiceHash mode is off.
2018-01-30 16:27:02.1411 [7] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #3.
2018-01-30 16:27:02.1511 [7] Built cryptonight program for Device #3.
2018-01-30 16:27:02.1511 [7] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:06.0069 [13] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:27:06.0074 [13] Reconnecting to the server...
2018-01-30 16:27:06.6739 [1] Stopping miners...
2018-01-30 16:27:06.6830 [9] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.6960 [18] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7155 [17] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7265 [10] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7380 [8] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7505 [16] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7621 [7] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7656 [12] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.8978 [1] Stopped miners.
no mine. stop all time 4x 480 4gb
2018-01-30 16:26:43.4776 [1] Saving settings to C:\Users\user\AppData\Roaming\GatelessGateSharp\Backups\2018-01-30--1626.sqlite...
2018-01-30 16:26:45.4514 [1] Saved settings.
2018-01-30 16:26:45.4915 [1] Launching miner(s) for Custom Pool 0...
2018-01-30 16:26:45.4920 [7] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:26:45.4925 [7] Reconnecting to the server...
2018-01-30 16:26:45.5155 [17] Miner thread for Device #0 started.
2018-01-30 16:26:45.5155 [17] NiceHash mode is off.
2018-01-30 16:26:45.5190 [17] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #0.
2018-01-30 16:26:45.5335 [17] Built cryptonight program for Device #0.
2018-01-30 16:26:45.5335 [17] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:45.6648 [16] Miner thread for Device #0 started.
2018-01-30 16:26:45.6648 [16] NiceHash mode is off.
2018-01-30 16:26:45.6678 [16] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #0.
2018-01-30 16:26:45.6748 [16] Built cryptonight program for Device #0.
2018-01-30 16:26:45.6748 [16] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:45.8134 [18] Miner thread for Device #1 started.
2018-01-30 16:26:45.8134 [18] NiceHash mode is off.
2018-01-30 16:26:45.8154 [18] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #1.
2018-01-30 16:26:45.8332 [18] Built cryptonight program for Device #1.
2018-01-30 16:26:45.8332 [18] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:45.9535 [8] Miner thread for Device #1 started.
2018-01-30 16:26:45.9535 [8] NiceHash mode is off.
2018-01-30 16:26:45.9570 [8] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #1.
2018-01-30 16:26:45.9744 [8] Built cryptonight program for Device #1.
2018-01-30 16:26:45.9744 [8] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:46.0983 [9] Miner thread for Device #2 started.
2018-01-30 16:26:46.0983 [9] NiceHash mode is off.
2018-01-30 16:26:46.1074 [9] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #2.
2018-01-30 16:26:46.1169 [9] Built cryptonight program for Device #2.
2018-01-30 16:26:46.1169 [9] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:46.2391 [10] Miner thread for Device #2 started.
2018-01-30 16:26:46.2391 [10] NiceHash mode is off.
2018-01-30 16:26:46.2416 [10] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #2.
2018-01-30 16:26:46.2496 [10] Built cryptonight program for Device #2.
2018-01-30 16:26:46.2496 [10] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:46.3927 [12] Miner thread for Device #3 started.
2018-01-30 16:26:46.3927 [12] NiceHash mode is off.
2018-01-30 16:26:46.4077 [12] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #3.
2018-01-30 16:26:46.4639 [12] Built cryptonight program for Device #3.
2018-01-30 16:26:46.4639 [12] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:46.5409 [13] Miner thread for Device #3 started.
2018-01-30 16:26:46.5409 [13] NiceHash mode is off.
2018-01-30 16:26:46.5444 [13] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #3.
2018-01-30 16:26:46.5519 [13] Built cryptonight program for Device #3.
2018-01-30 16:26:46.5519 [13] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:26:50.4927 [7] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:26:50.4932 [7] Reconnecting to the server...
2018-01-30 16:26:55.4936 [7] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:26:55.4941 [7] Reconnecting to the server...
2018-01-30 16:27:00.4952 [7] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:27:00.7109 [1] Stopping miners...
2018-01-30 16:27:00.7186 [8] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7201 [16] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7566 [9] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7756 [18] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7801 [17] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7891 [10] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.7916 [13] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.8101 [12] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:00.9398 [1] Stopped miners.
2018-01-30 16:27:00.9503 [1] Stopping miners...
2018-01-30 16:27:00.9893 [1] Stopped miners.
2018-01-30 16:27:01.0053 [1] Launching miner(s) for Custom Pool 0...
2018-01-30 16:27:01.0063 [13] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:27:01.0063 [13] Reconnecting to the server...
2018-01-30 16:27:01.0304 [12] Miner thread for Device #0 started.
2018-01-30 16:27:01.0309 [12] NiceHash mode is off.
2018-01-30 16:27:01.0349 [12] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #0.
2018-01-30 16:27:01.0429 [12] Built cryptonight program for Device #0.
2018-01-30 16:27:01.0429 [12] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.1982 [10] Miner thread for Device #0 started.
2018-01-30 16:27:01.1982 [10] NiceHash mode is off.
2018-01-30 16:27:01.2012 [10] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #0.
2018-01-30 16:27:01.2097 [10] Built cryptonight program for Device #0.
2018-01-30 16:27:01.2097 [10] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.3533 [9] Miner thread for Device #1 started.
2018-01-30 16:27:01.3533 [9] NiceHash mode is off.
2018-01-30 16:27:01.3564 [9] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #1.
2018-01-30 16:27:01.3674 [9] Built cryptonight program for Device #1.
2018-01-30 16:27:01.3674 [9] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.5071 [8] Miner thread for Device #1 started.
2018-01-30 16:27:01.5071 [8] NiceHash mode is off.
2018-01-30 16:27:01.5100 [8] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #1.
2018-01-30 16:27:01.5181 [8] Built cryptonight program for Device #1.
2018-01-30 16:27:01.5181 [8] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.6594 [18] Miner thread for Device #2 started.
2018-01-30 16:27:01.6594 [18] NiceHash mode is off.
2018-01-30 16:27:01.6624 [18] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #2.
2018-01-30 16:27:01.6815 [18] Built cryptonight program for Device #2.
2018-01-30 16:27:01.6820 [18] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.8110 [16] Miner thread for Device #2 started.
2018-01-30 16:27:01.8110 [16] NiceHash mode is off.
2018-01-30 16:27:01.8141 [16] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #2.
2018-01-30 16:27:01.8375 [16] Built cryptonight program for Device #2.
2018-01-30 16:27:01.8375 [16] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:01.9911 [17] Miner thread for Device #3 started.
2018-01-30 16:27:01.9911 [17] NiceHash mode is off.
2018-01-30 16:27:01.9946 [17] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #3.
2018-01-30 16:27:02.0021 [17] Built cryptonight program for Device #3.
2018-01-30 16:27:02.0026 [17] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:02.1376 [7] Miner thread for Device #3 started.
2018-01-30 16:27:02.1376 [7] NiceHash mode is off.
2018-01-30 16:27:02.1411 [7] Loaded BinaryKernels\Ellesmere_cryptonight_8.bin for Device #3.
2018-01-30 16:27:02.1511 [7] Built cryptonight program for Device #3.
2018-01-30 16:27:02.1511 [7] Build options: -O5 -IKernels -DWORKSIZE=8
2018-01-30 16:27:06.0069 [13] Exception in Stratum.StreamReaderThread(): System.Net.Sockets.SocketException (0x80004005): Host desconocido
en System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
en GatelessGateSharp.Stratum.StreamReaderThread()
2018-01-30 16:27:06.0074 [13] Reconnecting to the server...
2018-01-30 16:27:06.6739 [1] Stopping miners...
2018-01-30 16:27:06.6830 [9] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.6960 [18] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7155 [17] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7265 [10] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7380 [8] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7505 [16] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7621 [7] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.7656 [12] Exception in miner thread: Stratum server failed to send a new job. en GatelessGateSharp.OpenCLCryptoNightMiner.MinerThread()
2018-01-30 16:27:06.8978 [1] Stopped miners.
no mine. stop all time 4x 480 4gb
I figure out why GGS start to use CPU after large amount of time running with jumps from 0-1 to 14-15%.
It's due to updating log.
After clearing the log on log tab CPU usage drops to 0-2% like at GGS launch.
zawawa, you must do something this that. Maybe make limit of strings on the log tab? Because amout of that strings grows with time...
It's due to updating log.
After clearing the log on log tab CPU usage drops to 0-2% like at GGS launch.
zawawa, you must do something this that. Maybe make limit of strings on the log tab? Because amout of that strings grows with time...
The screen scaling problems still under 4k. Try different dpi sizes to reproduce!
https://www.imageupload.co.uk/images/2018/01/30/4kProblems.png
https://www.imageupload.co.uk/images/2018/01/30/4kProblems.png
The situation with gpu load looks like a little bit better in 1.2.13 version but it stil unstable, and i see a hashrate dance.. GGS settings is default. Guys can you check gpu load at neoscrypt algo?!
You just need to adjust overclocking setting to avoid power throttling.
Don't forget to lower the core voltage.
Hey Zawawa, could you please tell me, as I am trying to mine a NeoScrypt coin and I am using your miner for the first time and it is a bit confusing for me, where can I find the miner options? I mean how can I adjust clock and memory clocks, undervolting etc? I am mining on RX580 SE Sapphire Nitro+ and I am getting only 700-720mh/s, which IMO, watching other dudes performances, is quite low. I would like to check those settings, but I cannot find any information regarding my issue.
Also, could you please tell me where I'd be able to find information about the stats the miner is showing namely - https://imgur.com/a/fxZLq. - R/ HW/ WU??
700 - 720 kH/s not mh/s is normal neoscrypt speed for RX 580. Maybe 750...Also, could you please tell me where I'd be able to find information about the stats the miner is showing namely - https://imgur.com/a/fxZLq. - R/ HW/ WU??
So RX580 is getting the same as RX470? TF is this algo?
Gateless Gate Sharp 1.2.13 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.13-alpha
* Significantly reduced CPU usage.
* Added compatibility with screen scaling.
* Switched to Visual Studio 2017.
This new version came out pretty nice, methinks. Enjoy!
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.13-alpha
* Significantly reduced CPU usage.
* Added compatibility with screen scaling.
* Switched to Visual Studio 2017.
This new version came out pretty nice, methinks. Enjoy!
-Download CPU decreased by 1.5-2 times. (4-core)
-The idle time in the work of the GPU became less. Almost stable work.
Jump to: