[ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.4 (July 22)

[goedi]

First of all I want to thank you for creating this miner, and I know myself how much effort has to be put into software development, so I don't think 2% dev fee is a problem, especially if you get 10 times the sols you got before.

I tested it in a couple of different environments, all windows for the moment, linux will follow, all cards with stock settings:
1050ti => 5.5ksol
980 => 10ksol
290x => 7k
580 => 6.5ksol

tomorrow i should get 2 vega rx 56 will test them too then.

on one win10 pc i have the following:
Platform 0: NVIDIA CUDA, OpenCL 1.2 CUDA 9.1.83
   Device 0: GeForce GTX 980
Platform 1: AMD Accelerated Parallel Processing, OpenCL 2.0 AMD-APP (2442.12)
   Device 0: Hawaii
   Device 1: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Platform 2: Intel(R) OpenCL, OpenCL 2.0
   Device 0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz

trying tp run cpu under platform 1 make the miner crash immediately, under platform 2 it works however.

[Monayman]

Running fairly stable here on W10, except that when I shut off teamviewer, hash rate drops from 14ksols to 1500 sols...
Then jumps right back up when team viewer is turned on again.

Ideas?  

Edit: Removing hot fix solved speed issue, but now miner keeps crashing 

[Lolliedieb]

Running fairly stable here on W10, except that when I shut off teamviewer, hash rate drops from 14ksols to 1500 sols...
Then jumps right back up when team viewer is turned on again.

Ideas?  

TeamViewer generally eats graphic power, see here:
https://www.reddit.com/r/gpumining/comments/7mwgpc/high_gpu_usage_in_teamviewer_pc_mining/

@All that have problems with the --enable-nv-hotfix:
It seems that on some systems the current version is to aggressive. I will try an alternative variant in the next hours and hopefully find a solution that works for all users. If new one looks more promising, will be included in the next version.


PS: I currently had access to a Linux rig with 8 1080's all stock. Miner runs now for about 16 hours stable there without any crash. It happens that one of the instances looses connection, but reconnect worked fine for this ones.

[BtcBlack]

I'm testing with RX 460 4GB. Successful

[Monayman]

Running fairly stable here on W10, except that when I shut off teamviewer, hash rate drops from 14ksols to 1500 sols...
Then jumps right back up when team viewer is turned on again.

Ideas?  

TeamViewer generally eats graphic power, see here:
https://www.reddit.com/r/gpumining/comments/7mwgpc/high_gpu_usage_in_teamviewer_pc_mining/

@All that habe problems with the --enable-nv-hotfix:
It seems that on some systems the current version is to aggressive. I will try an alternative variant in the next hours and hopefully find a solution that works for all users. If new one looks more promising, will be included in the next version.

No sir, the other way around.
When I turn on team viewer, hash rate goes UP (1500 -> 14000)
When I turn the remote display (TV) OFF, hash rate goes DOWN.

Weird, huh?

This is both on the miner and poolside, btw. Like clockwork.

Added - Im also testing on 2x 1080s and one 980ti for now.
Would rather not linux this one.

[Lolliedieb]

The performance drops A LOT randomly, in my 1060s from 10000 to 2200 sols

Hi out there. I wanted to write a private message to you but I am not allowed to - may you contact me via PM how to get in contact about this?
Thanks



Else: Is there anyone out there having problems with the NV hotfix that is causes hash-rate to drop too much (on Nvidia of cause ... enabling this with Intel or AMD will likely kill your hashrate) and that is online right now?

If I get the new hotfix tested it is likely we will have an other release later today (I did not plan to do v 0.12, but fixed enough stuff to make it worth not to wait until v 0.2 which will come with new feats somewhere next days).

[qwep1]

  Имя coбытия пpoблeмы:   APPCRASH
  Имя пpилoжeния:   lolMiner-mnx.exe
  Bepcия пpилoжeния:   0.0.0.0
  Oтмeткa вpeмeни пpилoжeния:   5a82e1bf
  Имя мoдyля c oшибкoй:   libstdc++-6.dll
  Bepcия мoдyля c oшибкoй:   0.0.0.0
  Oтмeткa вpeмeни мoдyля c oшибкoй:   56be6eb2
  Кoд иcключeния:   c0000005
  Cмeщeниe иcключeния:   00000000000c66b6
  Bepcия OC:   6.1.7601.2.1.0.256.1
  Кoд языкa:   1049
  Дoпoлнитeльныe cвeдeния 1:   a637
  Дoпoлнитeльныe cвeдeния 2:   a6376028ded939d5a943c3d8429c4ac2
  Дoпoлнитeльныe cвeдeния 3:   ee42
  Дoпoлнитeльныe cвeдeния 4:   ee42532b49ea6cebba1f2ad6d0011676 win 7 64 bit 1080 driver 384

[ol92]

The performance drops A LOT randomly, in my 1060s from 10000 to 2200 sols

Hi out there. I wanted to write a private message to you but I am not allowed to - may you contact me via PM how to get in contact about this?
Thanks



Else: Is there anyone out there having problems with the NV hotfix that is causes hash-rate to drop too much (on Nvidia of cause ... enabling this with Intel or AMD will likely kill your hashrate) and that is online right now?

If I get the new hotfix tested it is likely we will have an other release later today (I did not plan to do v 0.12, but fixed enough stuff to make it worth not to wait until v 0.2 which will come with new feats somewhere next days).

Yes. Cf my post on page 5

On windows 10 x64 (without --enable-nv-hotfix)
1x1070 - 14.0-15.0
2x1070 - 10.0-10.5
3x1070 - 7.8-8.2
1x1050 - 5.0-5.2

On windows 10 x64 (with --enable-nv-hotfix)
1x1070 - 1.8-3.0
2x1070 - 1.8-3.0
3x1070 - 1.8-3.0
1x1050 - 5.0-5.2

On ubuntu 16.04 (with --enable-nv-hotfix)
3x1070 - 13.2-14.0 (core 150, mem 300)
4x1060 - 8.7-9.2 (core 100, mem 200)
5x1050ti - 5.3-5.8 (core 50, mem 0)


Best solution for linux, more hashes than optiminer
Uptime on linux 8 hours

I have similar behaviour on a titan xp. Far worse performance with --enable-nv-hotfix.

System : windows 10 (creator update)
cpu : xeon E5 2696V3 (18 cores @3.2ghz with microcode/bios hack).
With the hotfix enables, performance is aroung 5 instead of 22-23. Cpu usage is very low ( less thant 20% for a dedicated core). Without the hotfix, performance is good and cpu usage is near a full dedicated core.

[shana95]

Hi folks,

this is the thread for announcing lolMiner-mnx for mining MinexCoin (MNX) based on the Equihash 96/5 algorithm (please do not confuse this with Zcash / BitcoinGolds Equihash 200/9).

I know that I have a newbie account, so for all of you afraid of catching a virus or other malware: Please wait for first reports or try it on an USB linux installation with your primary drives detached and thus without risk.

The miner is developed from scratch (I started it as a learning project) and thus still is in beta phase.  If you have trouble with the miner or suggestions please report here below this post. I will be happy to maintain a list of frequently asked features and most pressing bugs and will provide regular updates.

New Version v 0.11 (Feb 13)

Here you can download the software:
For Windows click here (Version 0.11)
For Linux click here (Version 0.11)
Note: the Windows version was very untested before the first release and has some stability issues (see below). So if it runs on your system (can currently not be guarantied) please monitor the miner a while before leaving it unattended. For stable mining currently the combination Linux and Nvidia graphics is the best tested and most stable (and it is very fast, too). At the current time prefer Linux over Windows version if possible.


Version history:
v 0.11 beta:
Added a new command line parameter "--enable-nv-hotfix".
The parameter will reduce the required CPU utilization on Nvidia graphic cards. If you required 100 + x% CPU utilization (so one full core and parts of a second) it is likely that now you will need 10-15% + x. I can not get rid of the x because  this is for checking if the solution is below the target. On my 2.1 ghz CPU with a GTX 1080 attached CPU utilization went down from 115% to ~20%. This will also help running multiple instances for large rigs. Unfortunately one will loose about 1-2% of mining speed on Nvidia hardware when enabling the switch. Therefore - and because the loss may be even larger for other vendors - the hotfix has to be enabled by command line for each instance.

Added an automatic reconnect when the connection is broken.
When a share is submitted and there is no acceptance message by the pool for the next 10 seconds the miner will reconnect to the pool in order to get back a stable connection. This helps the miner not to hang.

v 0.1 beta:
Initial release for Linux and Windows


Usage:
If you run the miner without any parameters or only by specifying the device it will run in an benchmark mode for one minute and display the current hash-rate.

To see all commands understood by lolMiner-mnx run it with -h  or --help as only parameter.

For normal use the usage is very generic:
./lolMiner --server <pool address>  --port <pool port> --user <your username>.<your worker name> --pass <your password on pool>(defaulted to “x”)  

For all Nvidia miners:
The default OpenCL behavior of Nvidia drivers cause a very high CPU load that can make it impossible to run the miner in multiple instances for a large rig. Add  "--enable-nv-hotfix" to reduce the CPU load (and the hash-rate by about 1%) in order to reduce the CPU load.


There are always some questions regarding new software that I want to answer in a FAQ style. Here we go.

FAQ

Is this miner for CPU / GPU, and for which vendors?
It can be run on any device that can execute OpenCL 1.1 code. So CPU (Intel / AMD) as well as GPU (Intel / Nvidia / AMD). We have to admit that our testing systems are mainly Intel CPU with Nvidia graphics machines, so this is the best tested situation.

What are the system requirements for lolMiner-mnx?
You will need an 64 bit system running any Linux distribution or Windows 7 / 8 / 10.
Moreover the miner requires that an OpenCL driver for the devices you want to mine one is installed on your system.
The memory required for the OpenCL device depends on the device since the miner tries to utilize the device as good as possible. The maximum on device memory that was used by the miner by now is approximately 450 MB.

What hashrate can I expect from device x?
This massively depends on OS, driver, the hardware itself. Here are some numbers from our testing systems that we collected when testing the miner. If you run it successfully please report in this thread so we can extend the list.

Intel Core I5-6200U Notebook CPU (2C / 4T):
Ubuntu 16.04:  ~ 210 sol/s
Windows 7:     ~ 215 sol/s    (but hash-rate more volatile then under Linux due to power management)

Intel HD Graphic 520 Notebook GPU
Windows 7:       ~ 410 sol/s*

AMD Radeon 5770 (800 cores / 850 mhz):
Ubuntu 16.04 with LLVM mesa 17.2.4 open source drivers:     ~795 sol/s*

AMD Kaveri A10 7850K Integrated GPU  (512 cores / 600 mhz / 8GB DDR3 1866):
Ubuntu 17.10 with LLVM mesa 17.3.3 open source drivers:     ~810 sol/s*   
Windows 10 with AMD Adrenaline Edition 17.12.1 drivers:   ~950 sol/s*

Nvidia GTX 745 (Maxwell, 384 cores / 1058 mhz / 4gb DDR3)
Ubuntu 16.04 with Cuda 9.1.83:   ~ 1840 sol/s

Nvidia GTX 1080 (Pascal, 2560 cores / 1607 mhz / 8gb GDDR5X)
Red Hat Linux Server with Cuda 8.0.0:   ~13200 sol/s

*With parallel graphics output of the OS running

Is there any load intensity setting in lolMiner-mnx yet?
Well no. The miner will always mine as fast as possible. So if you want to stress your device less or mine more power efficient then you should use your device drivers to underclock / undervolt / whatever. I may add a feature like this in the future, but I am not sure yet when and how I will do this because it is a lot of effort to make this possible for all OpenCL devices (I tried to use as few vendor-specific code as possible to make it run on as many systems as possible).

Can I run lolMiner-mnx on multiple GPUs?
Yes and no. Currently each miner instance can handle only one OpenCL device, but you can select the device by adding --platform <number of desired OCL platform> and --device <number of device in platform> to the command line call. So you need one instance of the miner for every device. The support for running multiple devices over the same stratum connection is planned for one of the (near) future releases.

Is there a dev-fee on the software?
Yes. At the current time the software has a dev-fee of 2%.

Are do the displayed sol/s include the fee?
No, the miner displays in “what you see is what you get” style. You will only see the sol/s counting to your account and also only the share submits and accepts counting to your own bill.

Are there plans to lower the fee in the future? 2% is a bit much…
Well is it when you consider that this one is build from scratch – which took two month, it is faster then optiminer on certain graphic cards (more then 60% on my stock 1080) and that minexcoin has a relatively low issue rate?
I will use the fee respectfully with regard to the people paying it, so be assured: One of the first invests will be in some more up to date hardware to test and develop lolMiner-mnx on a broad platform. Further hereby I promise: If the price of Minexcoin passes 50 dollars for more then two weeks or I complete an other miner for an other coin, I will release a version of the miner with lower fee.
Also I promise that when I decide to stop the active development of lolMiner I will clean up and release the sources.

Why are the binary packages so large?
Well in fact the pure lolMiner-mnx binaries are small when I build it on my development system. In fact it is not much more then a stratum connector and some stuff for running the OpenCL code. But for the shipped version the Linux binary also includes all required libraries (boost, libstdc++…) except for the OpenCL library to make it just run out of the box.
On Windows the situation is different. I build the Windows binary under Linux using a cross compiler, so the miner ships with all the libraries that are required to run this g++ code on a Windows based system.
Overall the size is just this way to ensure everything needed is on board.


Known issues:
[ALL OS, NVIDIA] High CPU Utilization (Found by me, Confirmed by all NVidia Users here)
Reason:Nvidia has a busy wait for OpenCL kernel completion thats considered a but for over 6 years now, but is not yet fixed (in CUDA it is...)
Problem for Miners: High CPU utilization that may cause problems with CPU cooling. Also dropping hashrate when too many instances are active on the same rig with week CPU and instances may crash. For example an Intel Celeron 3855u may only run one instance of lolMiner currently, Core I5 with 4 physical cores may run up to 3 GPU. More then 4 GPU are currently only stable with Intel Server CPU or AMD Threadripper.
Expected Time to Fix: Fixed with version v 0.11, see release notes.

Ps: You will always require a strong CPU for Minexcoin anyways, since the found solutions have to be put twice to SHA256 to compare it with the target. This is currently done on CPU and since the high end Nvidia cards can reach up to 20k sol/s this is not easy for the CPU. I expect that when properly fixed the above mentioned Celeron may handle 4-6 GPU but if you have a larger rig it would be better mining an other coin on the other GPUs or have a more potent CPU in the rig.

[ALL OS] At slow / unstable Internet connection sometimes lolMiner still submits shares but server does not accept them (Found by me, Confirmed by an offline friend of mine)
Reason: Well - weak connection is always bad for mining. Often re-connect helps.
Problem for Miners: lolMiner does not detect this yet and thus sometimes computes but shares are not counted. So you can not leave the miner unattended.
Expected Time to Fix:  Fixed with version v 0.11, see release notes.

[Windows / Official AMD drivers] Miner starts, but reports 0 sol/s or Miner does not start up with CL-compile error (Confirmed by me)
Ps: I am confused... I could be certain that someone yesterday gave a Screenshot of this and reported it but now the post is gone. Why?
Reason: Unknown yet.
Problem for Miners: Can not mine.
Expected Time to Fix: I can reproduce the error (when using CPU part on my Kaveri machine), but do not know why this happens yet. Will require deeper investigation because it seems that the OpenCL code does not return what it should do (and what it does on other platforms...)
 
[Windows, Linux (?) / Official AMD drivers] Miner does not start up with CL-compile error (Found by me, Confirmed by qwep1 and ruckus_pro)
Reason: Some problem with the OpenCL code for some AMD OCL drivers. It is unknown yet if this is also true for Linux version. Linux version with Open Source drivers is stable (but slower)
Problem for Miners: Can not mine.
Expected Time to Fix: I can reproduce the problem on some ages old machine at home. I will have a look into the issue later today and hope to get rid of this within next week.

[Windows] Random crash during execution (Reported by AAile, Confirmed by Aeon_)
Reason I do not know yet. It may be that the Nvidia driver things that the App over-utilizes the card. Currently lolMiner has only a very few things done on CPU before the next iteration starts (because the SHA stuff is done in an other thread), so the pressure on the GPU is very high.
Problem for Miners: The miner can not leave the miner unattended.
Expected Time to Fix: I need more info about when this happens and why. I hope that I can get rid out of this with the CPU load fixes above. Else one countermeasure could be running an external demon that checks if the miner is still running and restart it when it does not. Also I consider inserting a parameter that lowers GPU utilization (but of cause this will cost hash-rate... maybe one finds a stable trade of). I thing at least 2 of this countermeasures will be implemented within next two weeks, hopefully earlier. But for a definite fix I have to find the exact reason first

What about Laptop mining? specs I5 7th gen processor , Nvidea Geforce 940Mx VGA.. is this specs enough to mine some XMR?

[Dirtpaw]

What about Laptop mining? specs I5 7th gen processor , Nvidea Geforce 940Mx VGA.. is this specs enough to mine some XMR?
[/quote]

This miner is for Minexcoin (MNX).

[Lolliedieb]

I have similar behaviour on a titan xp. Far worse performance with --enable-nv-hotfix.

System : windows 10 (creator update)
cpu : xeon E5 2696V3 (18 cores @3.2ghz with microcode/bios hack).
With the hotfix enables, performance is aroung 5 instead of 22-23. Cpu usage is very low ( less thant 20% for a dedicated core). Without the hotfix, performance is good and cpu usage is near a full dedicated core.

Would you allow me to send you a private message? Unfortunately the forum still indicates me as being a newbie and your settings currently does not allow me to send a message.

[Anon11073]

Oh, this miner is a wonderful performance!
I hope that stability improves and Dev fee goes down.

Thank you, Lolliedieb. Good job.

[Syth]

Not worthless at all: you can use a shell script for an automatic relaunch:
 in a .bat:

echo -------------------------------------------------------------------
echo Simple script to restart your miner software after a period of time
echo -------------------------------------------------------------------
echo:

set executable=lolMiner-mnx.exe
set commandline= --server mnx.suprnova.cc --port 7076 --user xxxxx  --pass x    --platform 1
set /a counter=0
:start
%executable% %commandline%
echo:
echo Restarting the software  (%counter%)
set /a counter+=1
echo:
echo:
goto start

Did you test this script for hours mining?
If you look back in this thread you'll see a different script that I posted.

At first I ran lolMiner directly from the batch file like yours does and seemed to work fine, restarting when miner stopped.
The issue I had was after ~6 hours of run time the cmd window of the batch running the miner crashed or simply closed completely.
That's why I changed the script to open a new cmd process with the miner running inside instead. restarting this cmd instead aswell.

Although the script that I posted is for multiple GPUs, this was not for me and I am only running a single card.

[Syth]

After mining for over 24 hours split evenly on the two pools I have mined under 0.1 MNX on each pool. (12 hours on each)
That's 0.18 MNX after 24+ hours of mining using 10KSol/s.
I know the pool stats aren't always that accurate but it should give an estimate of how many coins you would mine given the current difficulty.
When I started mining the pool reported 1.9 MNX/day, was down to ~1.5 at some point and now at ~1.8/day.

Are the pool stats way off or is there something I am not seeing here?


Also not sure if these issues are unreported:

I think I only get this one on the eu.minexpool.nl pool:

Code:

Reconnecting in 500ms
Warning: read_until: A connection was disconnected by the software on the host computer

Reconnecting in 500ms
Connected!
Subscribed to stratum server
New target received: 0000555555555555540000000000000000000000000000000000000000000000
Warning: Received job has wrong number of parameters!
9

And this is I think is coming at times of bad internet connection, so maybe not an issue with the miner:

Code:

Warning: Incomplete response
Submitting share
Average speed (5s): 9618.18 Sol/s
Average speed (5s): 9672.6 Sol/s
Warning: too long between share and accept. Trying to reconnect.
Reconnecting in 500ms
Connecting to stratum server eu.minexpool.nl:3333
Average speed (5s): Warning: read_until: A connection was disconnected by the software on the host computer
Warning: read_until: A connection was disconnected by the software on the host computer

Reconnecting in 500ms
Warning: read_until: A connection was disconnected by the software on the host computer
Reconnecting in 500ms
Warning: read_until: A connection was disconnected by the software on the host computer
Warning: read_until: A connection was disconnected by the software on the host computer

[Lolliedieb]

@ Syth:

Currently the miner tries to re-connect too often when it things that connection is lost. Next version will reduce the number of attempts and also give the connection more time for recovering.

From my experiments with my 24 hours run the earnings were accurate (on Optiminer pool) according to the pool luck. On minexpool I did not test but I know that difficulty is higher there, so on the long term the earnings should fit, but it can be more volatile on the short term. As always it is important that the average sol/s detected by pool (over one hour or more) fit to whan the miner displays on command line. Then the miner works well. Everything else is in the responsibility of the pool.

[Syth]

@ Syth:

Currently the miner tries to re-connect too often when it things that connection is lost. Next version will reduce the number of attempts and also give the connection more time for recovering.

From my experiments with my 24 hours run the earnings were accurate (on Optiminer pool) according to the pool luck. On minexpool I did not test but I know that difficulty is higher there, so on the long term the earnings should fit, but it can be more volatile on the short term. As always it is important that the average sol/s detected by pool (over one hour or more) fit to whan the miner displays on command line. Then the miner works well. Everything else is in the responsibility of the pool.

Adding something like --retries and --retry-delay would be nice or even backup pool options.
If you just allowed the program to exit after failing to reconnect the specified amount of --retries consecutively, it would allow us to simply run a new instance trying another pool automatically.

[Lolliedieb]

So, lets go for New Version 0.12

As usual here are die Download links:
Linux 64: Click Here
Windows 64: Click Here

Change log:

Changes to the "--enable-nv-hotfix" switch
The hotfix is now a bit less aggressive compared to v 0.11. It may be that the CPU load is slightly up compared to the previous version, but the new algorithm is doing better when recovering from a time with overall high CPU load. If the old version worked better at your side you can still download the old version v0.11 here (Win 64) and here (Lin 64) .

In general for the miner monitor the load during the first minutes of running. If you have an overall system load above 60% I would recoment running less instances of lolMiner and use the remaining graphic cards for mining with an other coin.

Fix of the "compile() error"
The miner now also runs on older AMD implementations with the official AMD drivers. The most ancient card I tried was a Radeon HD 7770 (GCN 1, released February 2012 (!) ) and it runs fine with about 600 sol/s when using Windows 10.

Fix of a "lucky user" bug.
There was one strange bug in the miner causing a segfault when too many solutions were found with one equihash run. Usually on average about 2 solutions are found, 4-5 can happen, but I had one report of 10 solutions in one run. v 0.11 was not prepared for this, but now it is ^^

Improvements to reconnect function.
Before there were multiple threads testing if the stratum connection is still valid and that may have issued a reconnect. This sometimes caused that thread #1 wanted to restart the reconnect attempt just started by thread #0. Now there is exactly one thread left that is able to issue a reconnect when an error is detected. Also after the first reconnection attempt the miner will now wait for 30 seconds to give the pool time to respond before the next reconnection attempt is taken.

Shipment with new libraries in Windows version
We had some reports about libstdc++ library crashes in Windows version. I updated all libraries in Windows version to newer versions. This does not guaranty that the stability issues are gone, but maybe the new versions help. At least I had no issues with the new versions in first testing.


New known issues:
Connection reseted by peer (Linux),  A connection was disconnected by the software on the host computer (Windows), Received job has wrong number of parameters! (both), All on minexpool.nl
I do not know yet why - either if this is a pool issue over the last two days or if this is an issue of the miner. At least the miner had some trouble connecting to the pool sometimes and receives irregular messages from this pool from time to time. The connection reseted by peer message often seems to affect the miner when no share was send in more than 90 seconds. Future will show if this is miner or pool bug and if there are efficient countermeasures to handle this. Currently I can observe that the miner is able to recover from the issue by reconnection, but of cause this lowers income when shares get lost and the miner is waiting for a reconnection attempt.  

Adding something like --retries and --retry-delay would be nice or even backup pool options.
If you just allowed the program to exit after failing to reconnect the specified amount of --retries consecutively, it would allow us to simply run a new instance trying another pool automatically.

I will definitely consider this as one possible feature for next release version. Good idea


----------
Current hash-rate of all lolMiners out there: ~1.9 to 2 Msol/s
Market share: ~3.5%

[ruckus_pro]

So, lets go for New Version 0.12

Fix of the "compile() error"
The miner now also runs on older AMD implementations with the official AMD drivers. The most ancient card I tried was a Radeon HD 7770 (GCN 1, released February 2012 (!) ) and it runs fine with about 600 sol/s when using Windows 10.

Thank you!!! this worked for me, but hash rate still lower than on optiminer for RX560 2500 vs 5000H/s

[Racquemis1]

Hi Lolliedeb, check your pm. Send you a message regarding the wrong parameters 'problem'

[Maza6]

Hello, my internet or computer seems to be so slow, that it doesn't have enough time to connect to the pool, before the program starts to spam pool with reconnections, and I get kicked out from the pool. I don't really think it should work that way? Sometimes I get connection in time, anyway, it loses usually approximetly in 1 hour and then it starts to spam that reconnect and again breaks down. Can you make it do those connection things bit more slowly. Like give it some more seconds to connect, and do it have to try to reconnect twise in second? It should really be OK to try like every 10 second?  

edit:

My Win10 computer with GTX 1080 gives this connection problem / bug and after a while whole program goes down. And in windows 7 i got another 1080 and 1050, these both dont work more than~10 seconds. After 10 seconds it just quits, with no warning at all. Picture under shows the connection bugging first on windows 7 computer, after it connects, it almost immidietly quits. With no message at all. And it does it with gtx1080 and 1050 both.

https://imgur.com/a/atk9k