Megaminer 6.3 - Multi pool / Multi Algo launcher

[mo35]

I'm testing the master-copy on github and it seems to be working.

btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?

yeah thos two are on top of wishlist too , imho must have features

[1713237568]

1713237568

[1713237568]

1713237568

[tutulfo]

I'm testing the master-copy on github and it seems to be working.

btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?

Switching threshold will be in next release, I wnat to close 5.0 stable release before.


What is Auto speed updating?

[mo35]

I'm testing the master-copy on github and it seems to be working.

btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?

Switching threshold will be in next release, I wnat to close 5.0 stable release before.


What is Auto speed updating?

Auto speed updating is updating hashrate stat files while in mining process , either implement second value or simply overwrite initial profiling value periodically.
Inital profiling isnt particulary accurate , it shaves off quite some margin using 200 sec profiling. So when profiling rig i have to manually enter actual values and usualy thos are quite a bit higher , than written after profiling period.

[geck]

I'm testing the master-copy on github and it seems to be working.

btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?

Switching threshold will be in next release, I wnat to close 5.0 stable release before.


What is Auto speed updating?

Auto speed updating is updating hashrate stat files while in mining process , either implement second value or simply overwrite initial profiling value periodically.
Inital profiling isnt particulary accurate , it shaves off quite some margin using 200 sec profiling. So when profiling rig i have to manually enter actual values and usualy thos are quite a bit higher , than written after profiling period.

yes and don't update (give an error message) if the hash rate is outside of the tolerance

[tutulfo]

I'm testing the master-copy on github and it seems to be working.

btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?

Switching threshold will be in next release, I wnat to close 5.0 stable release before.


What is Auto speed updating?

Auto speed updating is updating hashrate stat files while in mining process , either implement second value or simply overwrite initial profiling value periodically.
Inital profiling isnt particulary accurate , it shaves off quite some margin using 200 sec profiling. So when profiling rig i have to manually enter actual values and usualy thos are quite a bit higher , than written after profiling period.

This was implemented releases ago but some miners sometimes send hashrates peaks, until you see and correct that miner/algo was always running.

I deactivated this option to check only one time stats are right after benchmark

[tutulfo]

5.0 Release

*Better miners "close" mechanism (safer and more agrresive)
*Enhanced dynamic api port assignation, now is possible to run more than one instance of MM without ports conflicts.
*Added Excavator for NVIDIA
*Added Ccminer Nanashi
*Added XMrig msvc for CPU
*Updated ccminer klaust to 8.16
*Updated claymore crypto to 11.0
*Added AMD gpu info on current screen (experimental)

*Fixed: pool not recovering from fail when multiple pools running
*Fixed: xmrcast not selecting devices
*Fixed: new zpool api profit units for keccak
*Fixed: automatic log folder deletion not working
*Fixed: ccminer polytmos not allowing more than one instance


THIS VERSION REQUIRES 5.0 FORMAT CONFIG.TXT FILE, IF YOU UPGRADE FROM 4.X RELEASE YOU MUST DOWNLOAD AND CONFIGURE AGAIN!!!

[Jounouchi]

5.0 Release

*Better miners "close" mechanism (safer and more agrresive)
*Enhanced dynamic api port assignation, now is possible to run more than one instance of MM without ports conflicts.
*Added Excavator for NVIDIA
*Added Ccminer Nanashi
*Added XMrig msvc for CPU
*Updated ccminer klaust to 8.16
*Updated claymore crypto to 11.0
*Added AMD gpu info on current screen (experimental)

*Fixed: pool not recovering from fail when multiple pools running
*Fixed: xmrcast not selecting devices
*Fixed: new zpool api profit units for keccak
*Fixed: automatic log folder deletion not working
*Fixed: ccminer polytmos not allowing more than one instance


THIS VERSION REQUIRES 5.0 FORMAT CONFIG.TXT FILE, IF YOU UPGRADE FROM 4.X RELEASE YOU MUST DOWNLOAD AND CONFIGURE AGAIN!!!

Hi, sorry, may I know the 5.0 release version consists of CPU miners? As I don't see any configuration params in the txt file.

[Tasbi]

5.0 Release

*Better miners "close" mechanism (safer and more agrresive)
*Enhanced dynamic api port assignation, now is possible to run more than one instance of MM without ports conflicts.
*Added Excavator for NVIDIA
*Added Ccminer Nanashi
*Added XMrig msvc for CPU
*Updated ccminer klaust to 8.16
*Updated claymore crypto to 11.0
*Added AMD gpu info on current screen (experimental)

*Fixed: pool not recovering from fail when multiple pools running
*Fixed: xmrcast not selecting devices
*Fixed: new zpool api profit units for keccak
*Fixed: automatic log folder deletion not working
*Fixed: ccminer polytmos not allowing more than one instance


THIS VERSION REQUIRES 5.0 FORMAT CONFIG.TXT FILE, IF YOU UPGRADE FROM 4.X RELEASE YOU MUST DOWNLOAD AND CONFIGURE AGAIN!!!

Hi, sorry, may I know the 5.0 release version consists of CPU miners? As I don't see any configuration params in the txt file.

included on Config.txt

-- Use your cpu to mine: ENABLED = yes, DISABLED = no (you can start cpu alone mining also using -groupnames parameter in batch file)

@@CPUMINING=DISABLED

[Tasbi]

Hello,
Can´t mine LYRA2V2, hashrate is always 0
Using MPH
Have tried in 3 diferent rigs using nvidia GTX1060
here is an image

https://imgur.com/D5uMV1i

Any ideas on how to solve this?

[dudel42]

thanks for the 5.0 release, will try that later tonight.

is there a way to use 24 hour profitability instead of current prof. from the pool? i'd like to reduce algo switching, but long interval times work better with profit calculated over a longer time (like the last 24 hours).

[tutulfo]

Hello,
Can´t mine LYRA2V2, hashrate is always 0
Using MPH
Have tried in 3 diferent rigs using nvidia GTX1060
here is an image



Any ideas on how to solve this?

Same for me in other algos with excavator...I have no idea, somebody?

Lyra2v2 is covered by other miners, you can delete excavator miner file.

[sconklinbtc]

thanks for the 5.0 release, will try that later tonight.

is there a way to use 24 hour profitability instead of current prof. from the pool? i'd like to reduce algo switching, but long interval times work better with profit calculated over a longer time (like the last 24 hours).

For interval, you can change this in the config file:

Code:

-- Profit recheck interval time (in seconds - less than 600 not recommended)
-- This interval recalculates and selects the most profitable algorithm

@@INTERVAL=600

For using 24h profits, just change MiningMode from automatic to automatic24h in the bat file.

[Dan11i]

How well does this fair with nvidia gpus? I know they generally are not ideal but does it support any algos that are decent for them?

[sconklinbtc]

How well does this fair with nvidia gpus? I know they generally are not ideal but does it support any algos that are decent for them?

It just launches the typical miners you would see for nvidia GPUs...ccminer, ewbf, etc. So it's as good as those. Though it does test your mining speed on different algorithms against different variants of the previously mentioned miner to choose the most efficient variant to mine with.

[Tasbi]

Hello,
Can´t mine LYRA2V2, hashrate is always 0
Using MPH
Have tried in 3 diferent rigs using nvidia GTX1060
here is an image

https://imgur.com/D5uMV1i

Any ideas on how to solve this?

Same for me in other algos with excavator...I have no idea, somebody?

Lyra2v2 is covered by other miners, you can delete excavator miner file.

Yes this solved the problem... I just delete excavator miner file.
thanks, hope someone knows why this happens

[zoooz]

http://i102.fastpic.ru/big/2017/1219/51/6a4819585654b32d296b08cf1c639551.jpg
dual mining zpool

MPH/ZPOOL AMD and NVIDIA

[tutulfo]

How well does this fair with nvidia gpus? I know they generally are not ideal but does it support any algos that are decent for them?

It suport all algos compatible with Nvidia.

[sconklinbtc]

How well does this fair with nvidia gpus? I know they generally are not ideal but does it support any algos that are decent for them?

It suport all algos compatible with Nvidia.

I have to say, that's what I love about MM. It downloads all necessary miner and all variants, determines which is the most profitable with each algorithm during the benchmarking process, then makes sure you're mining the most profitable way possible within the parameters you set between the config file and the bat file.

[dudel42]

For using 24h profits, just change MiningMode from automatic to automatic24h in the bat file.

for which pools does automatic24h work (or does it work for all of them)?

[robl450]

How does automatic 24h work?  You switch algos once per day to whatever is best?

One thing I notice with this compared to multipool miner is that this one when benchmarking doesn't appear to figure out that something doesn't work and just keeps trying to launch over and over where multi pool miner will launch 3 times and give up.

one other thing. is there anyway to allow support for ethash 2gb instead of ethash or a way to just disable ethash as my card doesn't support ethash as it only is 2gb and just errors on every one of them when benchmarking.