This is not true. GTX 1060 with Samsung memory hashes a bit over 25 MH/s at 75 watts power limit? Wasting hashpower?

Patrike,

Could you add something to profit profile for me? Could you add under Profit Profile, when you select an algo from the list on the display under gpu clocking profiles start and stop, could you add a line for "execute batch file before start mining" then a selection to allow us to link to it either local or remotely.

This simple addon would allow people to use third party OC and Settings without a major overhaul to Awesome Miner.
Example on a remote rig, i could then create a folder for all my OC batch files, then create a new one for each algo like Skein.bat, then link to it so we can use Nvidia Inspector without you having to implement it and get rights to use someone elses software....

I decided to test out Nicehash vs Ahashpool again with my rig

both cards 1080ti's watercooled on same settings

GPU 1 Nicehash, 24hr profit 0.00024200 btc on single 1080ti using nicehash miner
GPU 2 Ahashpoolplus 24hr profit 0.00033000 btc on single 1080ti using nemo miner

Shouldn't be using estimates... Look at 24 hour actual values instead.  Hopefully you are testing with 3 identical rigs running concurrently and using ahashpoolplus with nplusminer 1.3

>>AHashPool beats NiceHash
^^^^^ imho it's your fanstasies, but lets test.

We are talking about zpool... It's not profitable under nemosminer?
I'm ready to test ahashpool. Teach me which algos to enable and which .bat use. ahashpool /  ahashpool24hr / ahashpoolPlus ?

Im try to 7h test NPlusMiner - аpprox $ 14.91531086 / day, disappointing result.

Plus Nicehack can operate at a loss until they need some more funds to continue then organise a convenient wallet hack… 

Believe me, after all the trash talking I've done about NiceHash (aka NiceHack), no one was more surprised as each and every multi-algo pool I've tested over the last month has come in 2nd place, and often by a startling amount. HashRefinery and Zergpool both brought in 30% less over their 1 week test period than NH. Granted, both pools happened to get on the wrong side of some hard-forks, but since that isn't something you have to worry about with NH I can't really toss out the comparisons as invalid. Both MiningPoolHub and Zpool came in around 10% less than NH over their test periods (1 week for MPH, only 3 days for Zpool) and given the limitations of my test setup I am inclined to call these a tie, but that's rather missing the point: the whole idea behind multi-algo, auto-switching pools is to beat single-coin mining AND NiceHash over time (if you are the type that either cashes out in fiat on a regular basis or just wants to accumulate BTC without buying a shitty ASIC).

And especially since NH is rather restricted in the algos it offers I am even more surprised at the poor showing of these multi-algo pools, but maybe it's not the pool's fault, maybe it's NemosMiner's, so I am contemplating trying another multi-algo miner manager next.

Awesome Miner version 4.4.4

- Improved failure detection for pools included in the profit switcher, to faster detect failures between the profit switching intervals
- Possible to manually reset the list of failed pools for a miner, to have the profit switcher consider them again. The feature can be access from the View Details dialog where the failed pools are listed.
- Excavator miner will only connect to a single pool (or two pools for dual mining)

Is it possible to set intensity of a miner for only 1 or 2 algorithms instead of all of them.
I added --intensity on the edit profit profile page

Hi patrike,

IMO, there needs to be an improvement for the performance tracking (graph) side, here are my opinions:
- how many times miners switched, what were the miners, what was the duration of mining?
- shared packages vs. miners vs. accepted/rejected vs. miner/algo
- hash speed vs. miner vs. algo (e.g. in time domain)
- mining vs. actual/24hr earning regarding to that (i think it is possible from the pool's api)

On the other side, mining the best two/three alternatives simultaneously (depending on the user choice) might be added:
- e.g. nicehash sometimes starts two threads for the half of the gpus for the first profitable option and for the second profitable one, this may reduce the fluctuation in earning.
- e.g. on non-homogenous systems, there may exist different gpus with different performance levels, some of them mines some algo best while the others can't, this may be a sol'n for that.

one final thing is manual intensity setting:
- alexis variants and kalust seems to using higher intensities (>25) for most algos, this may cause the system hang with gpus > 8; while tpruvot version goes well because of the constant i=20
- if there may be a constant intensity entry window for each algo, this may resolve the problem
- smart automatic intensity setting may be a second good feature of course, becase it seems the miner itself can not handle it well

thx a lot for your effort

@gak_45 It seems like you might have some misunderstanding of how a pool works and how different kind of share counting system works.  We're happy to provide some reference materials for you.

https://bitcointalk.org/index.php?topic=39832
https://en.bitcoin.it/wiki/Comparison_of_mining_pools

Since Phoenix is not yet supported by Awesome Miner, you need to input all your value like wallet pools on the config.txt on Phoenix Miner folder. Then go to your Awesome Miner and select your active miner > miner properties > mining engine and change it to Generic Miner(very bottom)  and then click browse and locate you phoenixminer.exe

but your solution/advice is not what I need or want.


Background: In Awesome Miner > Managed Software, there exists the ability to add a "User Defined command line argument"  for each supported Algo of the mining software. (in my case Ccminer/Phi)

Expectation:adding -i 20 or --intensity=20 to the "User Defined command line argument" results in CcMiner using an intensity of 20 for Phi algo

Result: CcMiner launches and closes within seconds, red error message shown too quickly to read. Log shows that the default -i 25 is included in the command line argument along with my user defined -i 20, causing CcMiner to crash

Resolution: user defined intensity should replace the default intensity

You did not understand the question.

Read again and test it yourself.

Try and unplug network cable to check in the simplest way. 

The problem is that if zpool is under DDOS attack, when ccminer tries to submit the shares it shows "connection refused" error. During this period AM does not update hashing rate and remains with the old hashrate for minutes or even hours. This is a big mistake from implementation algorithm because AM waits for updates from a miner that could be broken instead of AM having a computed hash rate per second that will solve a lot of problems like the one from above, when if you have 24 hours statistics you could have ccminer stucked for 12  hours or more instead of having it restarted (or switching to next one from statistics list) by AM like it suppose to do in a correct way.

Dear puwaha , next time try and understand and test things before writing wrong and misleading answers.

Have a nice day.
   

I've done this also. The problem is that you can not specify intensity for each algo for ccminer or every other miner.  
The window was closing in my case with the error "out of memory" for a part of the algos and i was able to view this with "Diagnostics" function from toolbar.

Having custom intensity settings specially for your GPU will increase your income by 30%. Default intensity values varies from one different chip to another but for example for Nvidia 1080 chip used on Gigabyte AORUS that is made from copper plate you will be able to get 20% more hash rate than a low end KFA2 1080 GPU that does not have copper pipes or copper plate, it has a small steel radiator.  So, ccminer does not know you have AORUS and it starts with minimal intensity settings for 1080, the same happens if you have water cooled gpu or the gpu rig submersed in mineral oil that offers huge overclocking advantage.

I believe this should be considered a priority by the developer of AM, instead of answering emails he should focus on fixing all issues with the software that are critical, because not taking an action and loosing money is as bad as AM crashing and being useles.

Have a great day.  

im also a little confused about the counts of shares submitted.

for about 225MH/s
claymore/phoenix reports submitting shares at a rate of about 78-80 shares/hr
but nanopool is seeing about 2x that number of shares at about 170 shares/hr

yet still seeing and calculating the same hashrate. can anyone explain this discrepancy?

It is really needed to have the possibility to add specific intensity values for each algo.

ccminer's default intensity is much less tan your GPU can handle. I tested with increasing intensity until crashing the miner and you can get 30% more has rate and more money for a part of the algos and AM really needs to have custom settings like it was requested in the past for each algo and not only for the miner like it is implemented right now.

ALSO:
I believe it would be better to show income statistics based on submitted (and also accepted shares) , instead AM not remains without any refresh to the last hash rate that was submitted by ccminer  even hours ago.

If AM waits for hours for an updated hashrate from ccminer that it has connection issues or it is not responding, and does not take time into consideration, it is not the correct behavior.
AM should have a timer that checks every x seconds the reported hashrate from the miner's API, with one minute delay when miner is started to allow all GPUs to be started and send hash rates. Like this if one pool / algo server is offline, it will change to the next most profitable algo from the list. RIGHT ?