Topic: [NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 186. (Read 289464 times)
Setting the interval to 3000 today.
Well, disabling Alexis didn't solve it for me. Rig crashed half a dozen times last night. The switching definitely does something my rig doesn't like... 
I've got 4Gigs of ram (do I need more?), set page file to 32 min - 64 max, gpus at 85% tdp, core offset +100... I'm out of ideas!
I've got 4Gigs of ram (do I need more?), set page file to 32 min - 64 max, gpus at 85% tdp, core offset +100... I'm out of ideas!
also increase mem
http://1stminingrig.com/best-windows-setup-configuration-tweaks-for-mining/
That's all i did and my rig is missmatched.
Make sure control panel... you are set to performance and also in windows set to performance
I don't think it's power related... I've got mobo and 2 cards on a 750W Gold and the other 3 on a 1000W Gold. I've looked at the logs, Alexis is the miner that crashes in 90% of cases. Tribus crashed twice too. Disabling them altogether and testing now again for 24 hours.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
I choose 4 algos
skein
neoscrypt
nist5
lyra2RE2
Then I took nemominer .... and made it so it mines at hashrefinery and at zpool.
https://mega.nz/#F!RPxCFBhB!ihNABH6KCFtebjOgdX1p3g if yah wanna try it out. Just change the btc address.
don't forget to mention you also need to change the name in start.bat from "NemosMiner-v2.0.6.ps1" to Ultimate_final.ps1
edit: also testing this now seeing how well it runs
dang. I changed it now. Thanks!
https://mega.nz/#F!RPxCFBhB!ihNABH6KCFtebjOgdX1p3g
updated link
I don't think it's power related... I've got mobo and 2 cards on a 750W Gold and the other 3 on a 1000W Gold. I've looked at the logs, Alexis is the miner that crashes in 90% of cases. Tribus crashed twice too. Disabling them altogether and testing now again for 24 hours.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
I choose 4 algos
skein
neoscrypt
nist5
lyra2RE2
Then I took nemominer .... and made it so it mines at hashrefinery and at zpool.
https://mega.nz/#F!RPxCFBhB!ihNABH6KCFtebjOgdX1p3g if yah wanna try it out. Just change the btc address.
don't forget to mention you also need to change the name in start.bat from "NemosMiner-v2.0.6.ps1" to Ultimate_final.ps1
edit: also testing this now seeing how well it runs
Well, disabling Alexis didn't solve it for me. Rig crashed half a dozen times last night. The switching definitely does something my rig doesn't like...
I've got 4Gigs of ram (do I need more?), set page file to 32 min - 64 max, gpus at 85% tdp, core offset +100... I'm out of ideas!
I've got 4Gigs of ram (do I need more?), set page file to 32 min - 64 max, gpus at 85% tdp, core offset +100... I'm out of ideas!
I don't think it's power related... I've got mobo and 2 cards on a 750W Gold and the other 3 on a 1000W Gold. I've looked at the logs, Alexis is the miner that crashes in 90% of cases. Tribus crashed twice too. Disabling them altogether and testing now again for 24 hours.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
I choose 4 algos
skein
neoscrypt
nist5
lyra2RE2
Then I took nemominer .... and made it so it mines at hashrefinery and at zpool.
https://mega.nz/#F!RPxCFBhB!ihNABH6KCFtebjOgdX1p3g if yah wanna try it out. Just change the btc address.
don't forget to mention you also need to change the name in start.bat from "NemosMiner-v2.0.6.ps1" to Ultimate_final.ps1
edit: also testing this now seeing how well it runs
Did anyone here figure out a solution to make Alexis miner load all 6 cards at once and fix the issue?
I don't think it's power related... I've got mobo and 2 cards on a 750W Gold and the other 3 on a 1000W Gold. I've looked at the logs, Alexis is the miner that crashes in 90% of cases. Tribus crashed twice too. Disabling them altogether and testing now again for 24 hours.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
I choose 4 algos
skein
neoscrypt
nist5
lyra2RE2
Then I took nemominer .... and made it so it mines at hashrefinery and at zpool.
https://mega.nz/#F!RPxCFBhB!ihNABH6KCFtebjOgdX1p3g if yah wanna try it out. Just change the btc address.
Two things:
1/ Intervals: If the switching was instant, you would be making most out of a short interval in theory. This is because, as said, you'd be nimbler to jump on whatever coin is most profitable at any point in time. Unfortunately, miners take time to switch. There's an initialization phase, every gpu starts up, sometimes it takes over a minute to get all your cards hashing. This is inefficient. So you can even this out by forcing your miner to stick around a bit longer per algo. I however do not believe you'd be doing yourself any favour by setting intervals longer than 10-15 minutes because you then lose that flexibility.
2/ Stability: My rig (5x 1080) is crashing several times a day with Nemosminer. I'm talking once an hour on avg. That's not good. On single coin it chugs along perfectly fine without reboots. I haven't yet been able to pinpoint the issue, so I can only *guess* either one instance of ccminer is unstable or the switching causes it.
1/ Intervals: If the switching was instant, you would be making most out of a short interval in theory. This is because, as said, you'd be nimbler to jump on whatever coin is most profitable at any point in time. Unfortunately, miners take time to switch. There's an initialization phase, every gpu starts up, sometimes it takes over a minute to get all your cards hashing. This is inefficient. So you can even this out by forcing your miner to stick around a bit longer per algo. I however do not believe you'd be doing yourself any favour by setting intervals longer than 10-15 minutes because you then lose that flexibility.
2/ Stability: My rig (5x 1080) is crashing several times a day with Nemosminer. I'm talking once an hour on avg. That's not good. On single coin it chugs along perfectly fine without reboots. I haven't yet been able to pinpoint the issue, so I can only *guess* either one instance of ccminer is unstable or the switching causes it.
Mine crashes with ccminer as well- sometimes it happened when I had gone to bed lol so I couldn't even turn it on until morning. 8 hours machine was idle.
I don't think it's power related... I've got mobo and 2 cards on a 750W Gold and the other 3 on a 1000W Gold. I've looked at the logs, Alexis is the miner that crashes in 90% of cases. Tribus crashed twice too. Disabling them altogether and testing now again for 24 hours.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
On a sidenote, the Spmod miner uses powershell... But that closes straight away for some reason and doesn't work at all. Very weird.
Two things:
1/ Intervals: If the switching was instant, you would be making most out of a short interval in theory. This is because, as said, you'd be nimbler to jump on whatever coin is most profitable at any point in time. Unfortunately, miners take time to switch. There's an initialization phase, every gpu starts up, sometimes it takes over a minute to get all your cards hashing. This is inefficient. So you can even this out by forcing your miner to stick around a bit longer per algo. I however do not believe you'd be doing yourself any favour by setting intervals longer than 10-15 minutes because you then lose that flexibility.
2/ Stability: My rig (5x 1080) is crashing several times a day with Nemosminer. I'm talking once an hour on avg. That's not good. On single coin it chugs along perfectly fine without reboots. I haven't yet been able to pinpoint the issue, so I can only *guess* either one instance of ccminer is unstable or the switching causes it.
1/ Intervals: If the switching was instant, you would be making most out of a short interval in theory. This is because, as said, you'd be nimbler to jump on whatever coin is most profitable at any point in time. Unfortunately, miners take time to switch. There's an initialization phase, every gpu starts up, sometimes it takes over a minute to get all your cards hashing. This is inefficient. So you can even this out by forcing your miner to stick around a bit longer per algo. I however do not believe you'd be doing yourself any favour by setting intervals longer than 10-15 minutes because you then lose that flexibility.
2/ Stability: My rig (5x 1080) is crashing several times a day with Nemosminer. I'm talking once an hour on avg. That's not good. On single coin it chugs along perfectly fine without reboots. I haven't yet been able to pinpoint the issue, so I can only *guess* either one instance of ccminer is unstable or the switching causes it.
Could be power related as when I first start mining on my 5 x 1080 ti rig with 1500W PSU and I noticed the cards will use full TDP briefly and it will do an impromptu reboot.
Never happens with EWBF but other miners can do it in the first minute or two
Two things:
2/ Stability: My rig (5x 1080) is crashing several times a day with Nemosminer. I'm talking once an hour on avg. That's not good. On single coin it chugs along perfectly fine without reboots. I haven't yet been able to pinpoint the issue, so I can only *guess* either one instance of ccminer is unstable or the switching causes it.
2/ Stability: My rig (5x 1080) is crashing several times a day with Nemosminer. I'm talking once an hour on avg. That's not good. On single coin it chugs along perfectly fine without reboots. I haven't yet been able to pinpoint the issue, so I can only *guess* either one instance of ccminer is unstable or the switching causes it.
Maybe your crashing issue arises with a certain algorithm that you do not ordinarily mine, or a certain version of CCminer that you do not ordinarily use. CCminer SP-Mod doesn't work at all on my machines, so I've disabled it.
Two things:
1/ Intervals: If the switching was instant, you would be making most out of a short interval in theory. This is because, as said, you'd be nimbler to jump on whatever coin is most profitable at any point in time. Unfortunately, miners take time to switch. There's an initialization phase, every gpu starts up, sometimes it takes over a minute to get all your cards hashing. This is inefficient. So you can even this out by forcing your miner to stick around a bit longer per algo. I however do not believe you'd be doing yourself any favour by setting intervals longer than 10-15 minutes because you then lose that flexibility.
2/ Stability: My rig (5x 1080) is crashing several times a day with Nemosminer. I'm talking once an hour on avg. That's not good. On single coin it chugs along perfectly fine without reboots. I haven't yet been able to pinpoint the issue, so I can only *guess* either one instance of ccminer is unstable or the switching causes it.
1/ Intervals: If the switching was instant, you would be making most out of a short interval in theory. This is because, as said, you'd be nimbler to jump on whatever coin is most profitable at any point in time. Unfortunately, miners take time to switch. There's an initialization phase, every gpu starts up, sometimes it takes over a minute to get all your cards hashing. This is inefficient. So you can even this out by forcing your miner to stick around a bit longer per algo. I however do not believe you'd be doing yourself any favour by setting intervals longer than 10-15 minutes because you then lose that flexibility.
2/ Stability: My rig (5x 1080) is crashing several times a day with Nemosminer. I'm talking once an hour on avg. That's not good. On single coin it chugs along perfectly fine without reboots. I haven't yet been able to pinpoint the issue, so I can only *guess* either one instance of ccminer is unstable or the switching causes it.
I was watching the zpool page for my wallet address & noticed that, for timetravel at least, a huge discrepancy between the hashrate recorded at zpool and what NemosMiner (or whatever ccminer he uses for timetravel) is actually hashing. I saw 150mh/s at my machine but only 1.5mh/s at zpool, and a 97.5% figure in the rejection column. The Ccminer window on my machine wasn't showing any rejections. So what is the real number? I usually see the number at zpool is way lower than what the actual mining software is reporting. Is this a problem with zpool's stat collection or is it because I am geographically a long way from zpool's server?
I have personally disabled timetravel algo on Nemos because zpool does not ever come close to correctly displaying its hashrate.
Also, earlier in this thread I see people discussing switching the "interval" because it is supposedly too low. I don't understand what difference this makes, but if the "profitability" of all these algos is changing very quickly, don't we want to change with it? I also don't understand where this "profitability" figure comes from or why it changes so often - but if something has a high profitability at any given time and we start mining it (but it changes often and quickly) aren't we likely to be mining something that WAS profitable when the measurement was taken, but if it's so volatile we are only doing well if it happens to stay high (which they rarely seem to)?
Essentially, one person has tested switching algos on NemosMiner at various time intervals to explore those various intervals' effects on profitability, but not to any degree which can be considered conclusive. All we can effectively say is that at the time he conducted the test, 3000-second intervals were performing the best for him.
I'm testing 30-min intervals right now.
Hi I just started with NemosMiner-v2.0.7-Zpool on a fresh install of Windows 8.1.
I was watching the zpool page for my wallet address & noticed that, for timetravel at least, a huge discrepancy between the hashrate recorded at zpool and what NemosMiner (or whatever ccminer he uses for timetravel) is actually hashing. I saw 150mh/s at my machine but only 1.5mh/s at zpool, and a 97.5% figure in the rejection column. The Ccminer window on my machine wasn't showing any rejections. So what is the real number? I usually see the number at zpool is way lower than what the actual mining software is reporting. Is this a problem with zpool's stat collection or is it because I am geographically a long way from zpool's server?
Also, earlier in this thread I see people discussing switching the "interval" because it is supposedly too low. I don't understand what difference this makes, but if the "profitability" of all these algos is changing very quickly, don't we want to change with it? I also don't understand where this "profitability" figure comes from or why it changes so often - but if something has a high profitability at any given time and we start mining it (but it changes often and quickly) aren't we likely to be mining something that WAS profitable when the measurement was taken, but if it's so volatile we are only doing well if it happens to stay high (which they rarely seem to)?
I was watching the zpool page for my wallet address & noticed that, for timetravel at least, a huge discrepancy between the hashrate recorded at zpool and what NemosMiner (or whatever ccminer he uses for timetravel) is actually hashing. I saw 150mh/s at my machine but only 1.5mh/s at zpool, and a 97.5% figure in the rejection column. The Ccminer window on my machine wasn't showing any rejections. So what is the real number? I usually see the number at zpool is way lower than what the actual mining software is reporting. Is this a problem with zpool's stat collection or is it because I am geographically a long way from zpool's server?
Also, earlier in this thread I see people discussing switching the "interval" because it is supposedly too low. I don't understand what difference this makes, but if the "profitability" of all these algos is changing very quickly, don't we want to change with it? I also don't understand where this "profitability" figure comes from or why it changes so often - but if something has a high profitability at any given time and we start mining it (but it changes often and quickly) aren't we likely to be mining something that WAS profitable when the measurement was taken, but if it's so volatile we are only doing well if it happens to stay high (which they rarely seem to)?
I'm in the same boat as you. 3 card 1080 Ti only returns about 5 mBTC per day recently.
Try editing your start.bat file and change "interval" from 90 to 1800
Try editing your start.bat file and change "interval" from 90 to 1800
Thanks for sharing. I'm gonna give it another 24 hours. Setting the interval to 900 now. We'll see.
If not better tomorrow I'll go back to NH.
This is pure conjecture because neither 900 interval nor 1800 interval were tested, but I think you will find better results with intervals at either 1800 or 3000. 900 interval is too close to 600 interval for me to recommend:
Order of earnings: Highest to Lowest for past 23hours
3000
6000
Default
600
36000
If you do find good results at 900, that will be a breakthrough and will buck the trend (first 13 hours had 6000 interval at best performance, @ 23 hours, 3000 had passed 6000 for best performance).
I'm testing today @ 1800 interval, then tomorrow @ 3000 interval.
The last day(admittedly profits are down) its making around the same that nicehash does.
0.00472944 BTC/day with 6x 1080's
With lower fees and such it is probably slightly more profitable.
0.00472944 BTC/day with 6x 1080's
With lower fees and such it is probably slightly more profitable.
ROFL!!!
Why Rofl?
Am I the only one getting this error
"Application has be blocked from accessing graphics hardware" 7-8 times in a row and then computer shuts down. Happened two days in a row and I wake up to a computer that has been rebooted. Losing all that mining time.
Edit- this time it happened with ccminer.exe - i don't remember if it was the same as last time.
"Application has be blocked from accessing graphics hardware" 7-8 times in a row and then computer shuts down. Happened two days in a row and I wake up to a computer that has been rebooted. Losing all that mining time.
Edit- this time it happened with ccminer.exe - i don't remember if it was the same as last time.
Hi,
I just added the jha algo and SWEEP coin to zpool.
Cheers
Can we mine that stuff with any ccminer version embedded in Nemosminer at all? I just added the jha algo and SWEEP coin to zpool.
Cheers
Tried ccminer-Alexis78 which was best among all other miners. hopefully this will best too. Gonna try today. ccminer-Alexis78 was really working awesome.
Jump to: