Topic: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.4 (July 22) - page 25. (Read 30772 times)

Lolliedieb,
some additions to your stat table:

Thanks for the work, but the 0.3 version gives less per 1000 s.s for the 1050 maps
The load parameter is now set not by a digit, but by the words 2G / AUTO / High, in my opinion this is a problem. on version 22, the 1050 card with load parameter 3 gives 6500ss, on version 0.3 it gives 5500 with a high
Maybe I'm setting the load parameter incorrectly ??

Good job! For each GTX1070 increase more than 1k/sol, and now 16-17k/sol. (Windows 10)
Uptime 20 min

The rest of the tests later

I sent you a PM Lolliedieb, containing my address to claim the reward.

Hi folks,

well it took some time for me, but finally it is there: lolMiner-mnx 0.3
And its the first month birthday of the miner as well - time to party 

As usual here are the download links:

Linux 64: Click me (v0.3)
Windows 64:  Click me (v0.3)

It will take a bit to describe what is new, so lets start.

Introduced a complete new Stratum Interface

As you may know the stratum interface of 0.22 was very buggy and caused serious problems on connection losses as well to the user as to the dev fee pool. Therefore 0.3 now has a complete new Stratum interface that should handle the situation much more gracefully and stable.

That said the new interface also comes with a new feature: fail-over support. You now can pass comma separated lists  to --server, --port, --user and --pass. The miner will try to connect to the first server in the list with the first credentials. Once there are too many reconnection attempts for this first connection the miner will go to the next pool in list with the 2nd user name and so on.
With --max-connection-attempts you can define how many connection attempts to be used before the miner switches over to the next pool & credentials in list. The default is 5.

This new stuff also applies for the dev fee connection. To bring this down the current three biggest pools have to be down simultaneously. Moreover the dev fee connection will try to use the same pool as the user for the fee, so the miner does no longer damage the balance of the pools by sending all shares to one pool. If this is not possible, it will do a round robin through all pools in the integrated list.

Even if the fee is completely blocked the miner will now continue to work, but slower then usual, because it will pause in between for reconnection attempts. The performance loss is approximately 5-10% depending on card and settings, but it will continue to work.

Improvement of the OpenCL code

As for the OpenCL code I did some performance improvements, that help hiding the memory latency (by almost 40%). This results the following performance table. I only listed the devices available for testing.

Nvidia

	lolMiner-mnx 0.22	lolMiner-mnx 0.3
GTX 970	unknown	10.2k sol/s
GTX 1060	9.9 - 10.1k sol/s	10.8-11.1k sol/s
GTX 1070ti	15.2k sol/s	17.5k sol/s
GTX 1080 FE	13.4k sol/s	17.1k sol/s
GTX1080 Ti	19.5k sol/s	22.5k sol/s

AMD

	lolMiner-mnx 0.22	lolMiner-mnx 0.3
RX 570 8GB	6.9k sol/s	8.9k sol/s
RX 580 4GB	7.4k sol/s	9.1k sol/s
RX 580 8GB	7.6k sol/s	9.8k sol/s
RX 580 4GB	9.9k sol/s	10.3k sol/s
with Mining BIOS
Vega 64	16k sol/s	~19k sol/s (to be confirmed)

All of the above numbers were generated with the Linux version of the miner with current amdgpu-pro or cuda drivers.

Note that the performance of AMD cards may be limited in Windows, see the commends to –set-work-batch below.

Beside this I added some new comfort features & changes:

--platform and –device
The platform parameter now understand the keyword AUTO, which is also default. This one will select the platform with the most graphic cards automatically. If there are two with the same number, e.g. and Intel integrated GPU and one AMD / Nvidia graphic card it will prefer the non-Intel platform.

Device now detects two special values ALL and ALLGPU (default), that will select all devices or all graphic cards in the selected platform. Note then when using --device ALL on a processor with integrated graphics the miner will mine as well on the integrated graphics and on the CPU part. For most configurations this is not recommended.

--set-work-batch
There are now three special values 2G, AUTO and HIGH. When the work batch is set to 2G the miner is allowed to use 2 gigabytes of graphic memory at most. At level AUTO it will use at most 60% of the graphic cards memory and at level HIGH 90%. Note that AUTO and HIGH operate on per-GPU level, so mixing graphic cards with different memory sizes is no problem.

For Windows and AMD graphic cards there currently is a problem with lolMiner-mnx and the driver preventing that the miner works with more then 2 gigabytes of memory. Therefore the default for the Windows version is 2G, while the default for the Linux version is AUTO. This causes lolMiner-mnx 0.3 to be slightly faster on Linux compared to Windows when using AMD graphic cards.

The restriction does not apply for Nvidia graphic cards. For this GPU it should be save to use AUTO on any operation system.

New parameter: --use-compact-short-stat

This parameter will make lolMiner-mnx to print the short statistics in a similar style as the long statistics but without the surrounding dashed lines. Therefore one single line will be used for all devices instead of one line per device.

New parameter:  --exit-on-zero

This parameter will cause lolMiner-mnx to check the speed of each device when printing out the long statistics. If an device is detected with 0 sol/s (thus it was idle on the long statistics intervall) the miner will quit, so it can be restarted from a watchdog script.

With all those changes I still may announce that working configuration files from 0.22 can be used with 0.3 and should work as before. But to use the new features you may like to modify it 

Beside the new comfort work I also tried to hunt down the memory access crashed and the reasons for reported 0 sol/s. This said it is natural that I may have overseen a problem, but it should be better now. If not please report.

That said there are two more smaller changes:
1. The dev fee is now reduced to 1.5% 
2. There is a new readme in .pdf file format shipped with the miner. This is now much closer to a real manual and should help to configure the miner


Bugs is a good keyword.
The fee collector collected slightly over 72 MNX for my early testers. That said I decided to round it up to 75 to make is a smooth number - or just because I have a good day 
But still I do not have all addresses yet, so here a remember to the following people still missing - Remember you have time until this Friday, 12:00 UTC  to claim your part (!)

From bitcointalk forum:

Code:

AAile
Anon11073
Atomsprengkopf
BtcBlack
ExEric3
gaissa
goedi
HarleyQuinn2011
Inves
Kompik
mikebzh44
Monayman
NameTaken
ol92
salshicha
Sebahl
Syth
TheG
Wa4A
YoloMolo
yurez83

From telegram:

Code:

crodair
Racquemis
Reagan
Valery

Beside this I will do one more announcement. Unfortunately I am not good enough in doing batch programming for a cool Watchdog, so I will put up an contest for that during next week. More details will follow.

Not a good behavior definitely. It's better to make overall hashrate lower by 2% if devfee connection is fail.

It's not strange, its well known: when miner cannot connect to developers pool to mine for devfee it also stops mining for you. Instead of just dev losing his 2% because his pool is down you also losing your 98%.

BobZilla1007, thank You, that was very helpful!

Hello everyone,
I am new to the forum and to mining in general (1st post)

I thought I would pop in and share a work around for the miner crashing on a windows box. It is not ideal but it will keep things going even when you are not available to attend to it.

Previously the miner would go along fine for anywhere between 20 min to several hours and then the windows crash report would pop up to where I would have to click close to get things going again.

I found this web page which explained how to circumvent the error reporting and solution seeking behavior. Now since I have used these procedures the miner will crash but instantly start back up automatically.

Here are the instructions I used. Make sure and change both settings as described. One deals with a dialog and the other a solution finding procedure.
https://www.raymond.cc/blog/disable-program-has-stopped-working-error-dialog-in-windows-server-2008/

I would like to ask the community which pool they think would be most profitable for a small rig like mine? I have tried both eu.minex and supernova.cc but I cannot determine which would be best, any thoughts?

I am running two GTX 1050TI cards in an OLD gaming rig (asus P6t Deluxev2 with 12GB corsair and an I7).

I know this is not much for mining but I did not build a new rig for mining, I just bought the cards to throw into a really old box I already had.

Thanks for your input ----BZ

Both rigs (miners) stopped with work, today at same time, about at 17h.
Just crashed.
These two rigs are in different location, both mining mnx with lolminer. Both use gtx1070.
Very strange.

The difficulty will be relative, in a few days when many are not profitable they will go.

Difficulty rose, and the LOL is unstable. I can not start all the cards, I have to launch a .bat for each card separately.

And if, the difficulty went up, we hope that the new version is more adjusted or in less than a week I will stop mining and prosecute with nemosminer.

There is still a lack of good documentation, as much as I try, I can not throw all the cards at once and if I do, just see one. I have read the documentation excasa several times, but it is normal, it is a beta product, I just hope it improves.

The fact that it barely gets hot, makes me wonder if you could get even more performance to the cards.

The maximum I've seen is 20,000 with 1080Ti Work 8 and a YouTube video paused behind.

I got those "0sol/s" for the first time on nvidia rig hour ago, I usually have that problem on amd rig.

After 30Mins of Mining with 3 GPUs (1080ti, 1070 % 1060) the Miner says 0SOL/s

diff gone to the Moon, and when consider that miner is not very stable - this coin it's not so profitable anymore... I was getting 0.25 mnx about every 3 hours, after last diff change I got 0.25 after 6 hours 

please tell me how long was the continuous testing? program is working stably on Ubuntu?

this is my result 
()is linux value
NVIDIA
1080Ti 17.5-19kH/s CC+150 mem+300(600) pl65
1080 13.5-14kH/s CC+150 mem+300(600) pl65
1070Ti 12.8-13.6kH/s CC+150 mem+300(600) pl65
1070 12-13kH/s CC+150 mem+300(600) pl70
1060 6GB 8.6-9.2kH/s CC+150 mem+0 pl70
1060 3GB 7.8-8.9kH/s CC+150 mem+0 pl70
1050Ti 6GB 5.6-6.2kH/s CC+150 mem+0 pl80

AMD
Vega FE 17.6-18.1kH/s CC 1350 @960mv Mem 1050 @960mv
Vega 64 16.3-17.1kH/s CC 1350 @920mv Mem 1050 @920mv
Vega 56 with samsungHBM 15.6-16.3kH/s CC 1350 @920mv Mem 945 @920mv
Vega 56 with hynixHBM 15.2-16.1kH/s CC 1350 @920mv Mem 890 @920mv
RX 570 4GB 8.4kH/s stock setting
RX560 4GB 4.1kH/s with ETH MOD BIOS

anyone have GT1030 and RX 550 result? 

set work batch 12 it's too high a value for 1070, in my 1070 rig it's stable in 7

I had a problem in that situation - the miner stopped working.