[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[Sibtigr]

Hello Patrice
By mining history

if you select statistics for 7 days or more, incorrect data is obtained!
that is, if one rig worked for a week then everything correctly displays 98-100 percent in the mining half.
And the second ring was added just a couple of days ago - in the statistics of mining time will be the same indicators for the week!

Hi.

The Mining Time is similar to an Uptime concept. If a more is added recently and is running most of the time, it will show up with 98-100%. Even if you added the miner two days ago and look at the the last week, Awesome Miner will still consider the mining time for this miner to be 98-100% because during the time the miner was present, it has been up all the time.

That is, it is essentially a useless tool turns out.
It is impossible to calculate the actual operation of the software. And bring the average hash rate.

Although those machines that have been idle in the middle of the week show and 65 percent of the work.
Is there any way to make this tool work?
To show the time of mining as in the time equivalent and percentage. As also shown, the average real hash rate. With the ability to export this data - when a lot of rigs.

Well, in General it is logical to understand if you put 3 days or 7 days - I want to get the percentage of the real work of machinery in this period...

[1715271396]

1715271396

[1715271396]

1715271396

[1715271396]

1715271396

[1715271396]

1715271396

[patrike]

Hello Patrice
By mining history

if you select statistics for 7 days or more, incorrect data is obtained!
that is, if one rig worked for a week then everything correctly displays 98-100 percent in the mining half.
And the second ring was added just a couple of days ago - in the statistics of mining time will be the same indicators for the week!

Hi.

The Mining Time is similar to an Uptime concept. If a more is added recently and is running most of the time, it will show up with 98-100%. Even if you added the miner two days ago and look at the the last week, Awesome Miner will still consider the mining time for this miner to be 98-100% because during the time the miner was present, it has been up all the time.

That is, it is essentially a useless tool turns out.
It is impossible to calculate the actual operation of the software. And bring the average hash rate.

Although those machines that have been idle in the middle of the week show and 65 percent of the work.
Is there any way to make this tool work?
To show the time of mining as in the time equivalent and percentage. As also shown, the average real hash rate. With the ability to export this data - when a lot of rigs.

Well, in General it is logical to understand if you put 3 days or 7 days - I want to get the percentage of the real work of machinery in this period...

To get access to hashrate and data export, please use the Mining History Export feature via the toolbar Tools -> Mining History Export. Many users running larger scale mining operations export hashrate, temperature, revenue, profit and mining uptime to CSV files that can be imported to Excel for further data processing.

For the mining time, Awesome Miner is currently indicating that as an uptime concept. It will be close to 100% unless you have actual downtime. If you add a new miner and it's running all the time, it will not be considered 0% uptime before it even was created. Only the time the miner existed in Awesome Miner will be counted here.

The main purpose of "Mining time" is to find miners not performing well and the current concept works fine for that purpose. Any miner with < 90% is indicating that it's not performing well. This is why showing low percentage for recently added miners (that do perform well) may not be preferred by many users. Especially if you have many miners and cannot really keep track of which ones you added recently.

I suppose this is where you rather would like it to show as 50% uptime for the last 7 days if the miner was added in the middle of the week - even if it's been working perfectly fine all the time. Is that a correct interpretation of your request here?

[Sibtigr]

I suppose this is where you rather would like it to show as 50% uptime for the last 7 days if the miner was added in the middle of the week - even if it's been working perfectly fine all the time. Is that a correct interpretation of your request here?

[/quote]

Yes, that's what I'd like

Ideal when you can export or view the data:
1 - how many actually worked for setting the time
2 - how many have been collected the ball, Rajkot and reboots
3 - average hashrate and average temperature

[trucobit]

A technical question Patrike

The other day you told me that you do not take into account the blocking time to calculate the auto profit, it surprised me a lot. Because the reward + blocking time determines the amount of maximum coins produced per day.

A coin with 2 minutes of blocking and 100 of reward, will make a maximum of 72,000 coins a day, but if the time of blocking is 1 minute will make 144,000 coins per day

How can profit be calculated without this data?
  In AM CU I asked for it and I see it logical. There are coins with blocking time of 5 and up to 10 minutes.

How can you compensate for that lack of this data in the system of self-profit, when it is crucial to know how often it will give a block and therefore reward and therefore profit.

There are two ways of calculating coins per day. In both cases you need to multiply the result with your hashrate as well.

You can find out coins per day by using one of these concepts:
1) Block Reward, Difficulty, Exponential Factor
2) Block Reward, Network Hashrate, Block Time

Awesome Miner uses #1, where the Difficulty in combination with Exponential Factor gives similar results as using the Network Hashrate in combination with Block Time. It's basically two different formulas.

The Block Time and Network hashrate impacts the Difficulty property of the coin - and this is why Awesome Miner doesn't have to use Block Time directly as it's already "included" as part of the Difficulty.

If so, then it works. But is not it easier to know the blocking time than the exponential factor? They are just my doubts.

[trucobit]

Hello Patrice
By mining history

if you select statistics for 7 days or more, incorrect data is obtained!
that is, if one rig worked for a week then everything correctly displays 98-100 percent in the mining half.
And the second ring was added just a couple of days ago - in the statistics of mining time will be the same indicators for the week!

Hi.

The Mining Time is similar to an Uptime concept. If a more is added recently and is running most of the time, it will show up with 98-100%. Even if you added the miner two days ago and look at the the last week, Awesome Miner will still consider the mining time for this miner to be 98-100% because during the time the miner was present, it has been up all the time.

That is, it is essentially a useless tool turns out.
It is impossible to calculate the actual operation of the software. And bring the average hash rate.

Although those machines that have been idle in the middle of the week show and 65 percent of the work.
Is there any way to make this tool work?
To show the time of mining as in the time equivalent and percentage. As also shown, the average real hash rate. With the ability to export this data - when a lot of rigs.

Well, in General it is logical to understand if you put 3 days or 7 days - I want to get the percentage of the real work of machinery in this period...

To get access to hashrate and data export, please use the Mining History Export feature via the toolbar Tools -> Mining History Export. Many users running larger scale mining operations export hashrate, temperature, revenue, profit and mining uptime to CSV files that can be imported to Excel for further data processing.

For the mining time, Awesome Miner is currently indicating that as an uptime concept. It will be close to 100% unless you have actual downtime. If you add a new miner and it's running all the time, it will not be considered 0% uptime before it even was created. Only the time the miner existed in Awesome Miner will be counted here.

The main purpose of "Mining time" is to find miners not performing well and the current concept works fine for that purpose. Any miner with < 90% is indicating that it's not performing well. This is why showing low percentage for recently added miners (that do perform well) may not be preferred by many users. Especially if you have many miners and cannot really keep track of which ones you added recently.

I suppose this is where you rather would like it to show as 50% uptime for the last 7 days if the miner was added in the middle of the week - even if it's been working perfectly fine all the time. Is that a correct interpretation of your request here?

when you add the times you made the change, and know how many times I change each coin to get the% they have. For me it is an important fact to know if a currency with a small percentage has many changes, it is a currency that I do not want to undermine. It would be nice to have that data in that panel of statistics next to the% of time of use of that currency.

[yrk1957]

@patrike - Can you add an option (in miner properties) to use average hash rate to calculate profit instead of 5s hash rate? Some miners have wild fluctuations in 5s rate, which does not give right figures.

[moppidoo]

A technical question Patrike

The other day you told me that you do not take into account the blocking time to calculate the auto profit, it surprised me a lot. Because the reward + blocking time determines the amount of maximum coins produced per day.

A coin with 2 minutes of blocking and 100 of reward, will make a maximum of 72,000 coins a day, but if the time of blocking is 1 minute will make 144,000 coins per day

How can profit be calculated without this data?
  In AM CU I asked for it and I see it logical. There are coins with blocking time of 5 and up to 10 minutes.

How can you compensate for that lack of this data in the system of self-profit, when it is crucial to know how often it will give a block and therefore reward and therefore profit.

There are two ways of calculating coins per day. In both cases you need to multiply the result with your hashrate as well.

You can find out coins per day by using one of these concepts:
1) Block Reward, Difficulty, Exponential Factor
2) Block Reward, Network Hashrate, Block Time

Awesome Miner uses #1, where the Difficulty in combination with Exponential Factor gives similar results as using the Network Hashrate in combination with Block Time. It's basically two different formulas.

The Block Time and Network hashrate impacts the Difficulty property of the coin - and this is why Awesome Miner doesn't have to use Block Time directly as it's already "included" as part of the Difficulty.

Hi Patrike,

Small requests as related to the above discussion if possible.

1) Include (non-dynamic) properties to set block time for coins (CTM happens to return 0 for a good number of them, and I'm being maths incompetent, would prefer method 2 above for calculation in Excel regarding possibility of solo mining)

1-1) (Not Important), most wallet JSON can report time elapsed since last block was solved (I think in seconds, or relative linux UTC timestamp), again, might be useful if this metric can be included for solo-mining (also display via AM HTTP API response (GET http://mypc:17790/api/coins/stats method) and coins tab)

2) Include (dynamic) properties to fetch network hash rate via custom sources (again, CTM is either displaying 0 or mostly incorrect data as sometimes Yiimp pool APIs it uses report hashrate incorrectly), again, this is probably going to be useful metric for solo-mining.

***Really want to have feature***
3) Ability to set pool profit factor via HTTP-API

Best Regards,

[joseph32]

Hey Patrik,

in the benchmark you can only bench 1 card at a time or all together. Is it possible to change this to multiple selectable cards, like bench with just the cards number 2, 4, 5 and 8?

Maybe with a selectable mark at the left side and two buttons "Select All" and "Select None" at the bottom. But if so, please select all cards as the pre-filled standard.

This would be awesome for multiple cards rigs to bench just specific cards together.

[Sibtigr]

I have been using the program for several years and have several editions.
Was certainly unpleasant moments, but mostly everything was great!
But sometimes we run into some wall of misunderstanding or something.
Is it not possible to raise the local server distribution of programs miners from the server directly from which we control the machines?
Why load programs miner with servers? after all, it is much easier to distribute programs miners from a local server?

According to the statistics of mining - well, the idea is good but the implementation in the form of an incomprehensible concept is absolutely not clear! if there is a tab or stobar time Malinga then why is it in percent? and it is not clear how to use it if you see one and in fact get absolutely other data in the concept!!!
export data again, if it is in practice, its use is not very clear because it is not very convenient!
Generally want highly user-friendly interface and get very difficult and sometimes not logical mega the product.
Manage a large number of machines really convenient. But want normal improvements!
Great solution for ispolzovany GPU is super! but after the fall of the program. - dispersal of flies!
1. Want much direct local server storage miners! In order not to load and not to rule the path of the program from third-party sources.
2. Statistiku time as one and a pack of cars.
3. Failure and crash statistics
4. your own VPN service
5. statistics on accepted balls and bad balls - because they are reset in the program window after a restart of the miner...
Now it's almost all sold - but alas it is not convenient and hard to understand

Let's all be on the same wavelength ponimanija not like now - here is your instrument, do with it what you want - to fix and finish will all not soon!
And prices!
For branding 800 dollars!!! it's just too much!
include at least in the basic package of 100 machines for free!

Of course, you have done a lot of work in a few years and I think more will be done. Well, let's any way to communicate! let's discuss innovations - for example to vote for new features which are well, just really need and put them in priority order!

Hope you will understand

[patrike]

A technical question Patrike

The other day you told me that you do not take into account the blocking time to calculate the auto profit, it surprised me a lot. Because the reward + blocking time determines the amount of maximum coins produced per day.

A coin with 2 minutes of blocking and 100 of reward, will make a maximum of 72,000 coins a day, but if the time of blocking is 1 minute will make 144,000 coins per day

How can profit be calculated without this data?
  In AM CU I asked for it and I see it logical. There are coins with blocking time of 5 and up to 10 minutes.

How can you compensate for that lack of this data in the system of self-profit, when it is crucial to know how often it will give a block and therefore reward and therefore profit.

There are two ways of calculating coins per day. In both cases you need to multiply the result with your hashrate as well.

You can find out coins per day by using one of these concepts:
1) Block Reward, Difficulty, Exponential Factor
2) Block Reward, Network Hashrate, Block Time

Awesome Miner uses #1, where the Difficulty in combination with Exponential Factor gives similar results as using the Network Hashrate in combination with Block Time. It's basically two different formulas.

The Block Time and Network hashrate impacts the Difficulty property of the coin - and this is why Awesome Miner doesn't have to use Block Time directly as it's already "included" as part of the Difficulty.

If so, then it works. But is not it easier to know the blocking time than the exponential factor? They are just my doubts.

There are cases where the NetHash+BlockTime formula doesn't produce the same results, but ideal would probably be for Awesome Miner to allow using any of them in the future

[patrike]

@patrike - Can you add an option (in miner properties) to use average hash rate to calculate profit instead of 5s hash rate? Some miners have wild fluctuations in 5s rate, which does not give right figures.

Thanks for the suggestion. Is this specifically with ASIC miners in mind where they report their own average hash rates? Most GPU mining software only report the current value, so in that case Awesome Miner would have to calculate the average over a period of time.

[patrike]

A technical question Patrike

The other day you told me that you do not take into account the blocking time to calculate the auto profit, it surprised me a lot. Because the reward + blocking time determines the amount of maximum coins produced per day.

A coin with 2 minutes of blocking and 100 of reward, will make a maximum of 72,000 coins a day, but if the time of blocking is 1 minute will make 144,000 coins per day

How can profit be calculated without this data?
  In AM CU I asked for it and I see it logical. There are coins with blocking time of 5 and up to 10 minutes.

How can you compensate for that lack of this data in the system of self-profit, when it is crucial to know how often it will give a block and therefore reward and therefore profit.

There are two ways of calculating coins per day. In both cases you need to multiply the result with your hashrate as well.

You can find out coins per day by using one of these concepts:
1) Block Reward, Difficulty, Exponential Factor
2) Block Reward, Network Hashrate, Block Time

Awesome Miner uses #1, where the Difficulty in combination with Exponential Factor gives similar results as using the Network Hashrate in combination with Block Time. It's basically two different formulas.

The Block Time and Network hashrate impacts the Difficulty property of the coin - and this is why Awesome Miner doesn't have to use Block Time directly as it's already "included" as part of the Difficulty.

Hi Patrike,

Small requests as related to the above discussion if possible.

1) Include (non-dynamic) properties to set block time for coins (CTM happens to return 0 for a good number of them, and I'm being maths incompetent, would prefer method 2 above for calculation in Excel regarding possibility of solo mining)

1-1) (Not Important), most wallet JSON can report time elapsed since last block was solved (I think in seconds, or relative linux UTC timestamp), again, might be useful if this metric can be included for solo-mining (also display via AM HTTP API response (GET http://mypc:17790/api/coins/stats method) and coins tab)

2) Include (dynamic) properties to fetch network hash rate via custom sources (again, CTM is either displaying 0 or mostly incorrect data as sometimes Yiimp pool APIs it uses report hashrate incorrectly), again, this is probably going to be useful metric for solo-mining.

***Really want to have feature***
3) Ability to set pool profit factor via HTTP-API

Best Regards,

Thanks for the suggestions.

For 1 and 2 I suppose we would also let Awesome Miner use the NetHash formula if for example the coin Difficulty is zero. Have you had a chance to test if this formula gives accurate numbers?
CoinsPerDay = hashRate / (hashRate + nethash) * secondsPerDay / blocktime * reward

3) Today you can only set Profit Factor for a Coin over the API, but not for a pool. If it's needed for pools as well it should be easy to add.

[patrike]

Hey Patrik,

in the benchmark you can only bench 1 card at a time or all together. Is it possible to change this to multiple selectable cards, like bench with just the cards number 2, 4, 5 and 8?

Maybe with a selectable mark at the left side and two buttons "Select All" and "Select None" at the bottom. But if so, please select all cards as the pre-filled standard.

This would be awesome for multiple cards rigs to bench just specific cards together.

Hello. In most scenarios it's better to benchmark a single GPU and save it to a Profit Profile. You can then use Profile Groups to create combinations of GPU's if needed, for example one nVidia 1070 + two nVidia 1080. As long as you have similar cards in terms of clockng across many miners, you can then reuse the same results across many miners.

In you case, are these cards all the same or a mix?

[patrike]

I suppose this is where you rather would like it to show as 50% uptime for the last 7 days if the miner was added in the middle of the week - even if it's been working perfectly fine all the time. Is that a correct interpretation of your request here?

Yes, that's what I'd like

Ideal when you can export or view the data:
1 - how many actually worked for setting the time
2 - how many have been collected the ball, Rajkot and reboots
3 - average hashrate and average temperature

Via the Mining History Export, where you can export CSV, you can at least find out #1 and #3.

For #2 I only understood the part about reboots and those are not recorded here, only via the notifications. It's however a good point to have statistics for this as well.

I have been using the program for several years and have several editions.
Was certainly unpleasant moments, but mostly everything was great!
But sometimes we run into some wall of misunderstanding or something.
Is it not possible to raise the local server distribution of programs miners from the server directly from which we control the machines?
Why load programs miner with servers? after all, it is much easier to distribute programs miners from a local server?

According to the statistics of mining - well, the idea is good but the implementation in the form of an incomprehensible concept is absolutely not clear! if there is a tab or stobar time Malinga then why is it in percent? and it is not clear how to use it if you see one and in fact get absolutely other data in the concept!!!
export data again, if it is in practice, its use is not very clear because it is not very convenient!
Generally want highly user-friendly interface and get very difficult and sometimes not logical mega the product.
Manage a large number of machines really convenient. But want normal improvements!
Great solution for ispolzovany GPU is super! but after the fall of the program. - dispersal of flies!
1. Want much direct local server storage miners! In order not to load and not to rule the path of the program from third-party sources.
2. Statistiku time as one and a pack of cars.
3. Failure and crash statistics
4. your own VPN service
5. statistics on accepted balls and bad balls - because they are reset in the program window after a restart of the miner...
Now it's almost all sold - but alas it is not convenient and hard to understand

Let's all be on the same wavelength ponimanija not like now - here is your instrument, do with it what you want - to fix and finish will all not soon!
And prices!
For branding 800 dollars!!! it's just too much!
include at least in the basic package of 100 machines for free!

Of course, you have done a lot of work in a few years and I think more will be done. Well, let's any way to communicate! let's discuss innovations - for example to vote for new features which are well, just really need and put them in priority order!

Hope you will understand

Thanks for the feedback.

1) You can customize the location from where the mining software is downloaded. Via the Options dialog, Managed Software section, you can edit specific mining software and either point it to another HTTP-server or to a Windows file share (\\servername\folder) from where all Remote Agents will do automatic download of mining software.

2) If I understand you point about the statistics correctly is that you want more information presented as an overview in the Mining History dialog, rather than having to use the Export feature to get all details. The Mining History can be improved to some extent, but if you want more powerful processing of the data and more flexibility, the Export feature is still more complete as it provides the raw data.

3) Good point. I had similar requests in the past and this is noted and will most likely be improved in the future

4) That's in the pipeline and will be part of Cloud Services. The first release of this feature will probably be for GPU miners, but the next step is to allow using the Remote Proxy for ASIC miners on remote sites and have them communicate with Awesome Miner via Cloud Services without the need of a VPN network or firewall configuration.

5) Is it statistics on Accepted/Rejected shares you are requesting? Maybe the accepted percentage would make sense, but I'm not sure how important the actual numbers would be.

About branding, it's not much for those that really require a branded product. It's mainly for those running professional companies hosting solutions for their clients, and they want their company name and logo to show up in the web interface. For these companies, the price isn't an issue. Compared to what other products out there charge for similar branding services, I would say that the price is quite low.

Thanks!

[joseph32]

Hey Patrik,

in the benchmark you can only bench 1 card at a time or all together. Is it possible to change this to multiple selectable cards, like bench with just the cards number 2, 4, 5 and 8?

Maybe with a selectable mark at the left side and two buttons "Select All" and "Select None" at the bottom. But if so, please select all cards as the pre-filled standard.

This would be awesome for multiple cards rigs to bench just specific cards together.

Hello. In most scenarios it's better to benchmark a single GPU and save it to a Profit Profile. You can then use Profile Groups to create combinations of GPU's if needed, for example one nVidia 1070 + two nVidia 1080. As long as you have similar cards in terms of clockng across many miners, you can then reuse the same results across many miners.

In you case, are these cards all the same or a mix?

Hey Patrik,

its mixed. Different brands, different models, different clocks. So it makes no sense to bench a single card and just multiple it or something similar. Benching a few cards together to run them in one profile, and benching other cards together to run in a different profile, and so on, is the idea behind. But maybe someday you find this idea great too and implement it

[yrk1957]

@patrike - Can you add an option (in miner properties) to use average hash rate to calculate profit instead of 5s hash rate? Some miners have wild fluctuations in 5s rate, which does not give right figures.

Thanks for the suggestion. Is this specifically with ASIC miners in mind where they report their own average hash rates? Most GPU mining software only report the current value, so in that case Awesome Miner would have to calculate the average over a period of time.

Yes, it’s for ASICs like Zig Z1, Antminer Z9, Antminer B7 etc.

[moppidoo]

Hi Patrike,

Small requests as related to the above discussion if possible.

1) Include (non-dynamic) properties to set block time for coins (CTM happens to return 0 for a good number of them, and I'm being maths incompetent, would prefer method 2 above for calculation in Excel regarding possibility of solo mining)

1-1) (Not Important), most wallet JSON can report time elapsed since last block was solved (I think in seconds, or relative linux UTC timestamp), again, might be useful if this metric can be included for solo-mining (also display via AM HTTP API response (GET http://mypc:17790/api/coins/stats method) and coins tab)

2) Include (dynamic) properties to fetch network hash rate via custom sources (again, CTM is either displaying 0 or mostly incorrect data as sometimes Yiimp pool APIs it uses report hashrate incorrectly), again, this is probably going to be useful metric for solo-mining.

***Really want to have feature***
3) Ability to set pool profit factor via HTTP-API

Best Regards,

Thanks for the suggestions.

For 1 and 2 I suppose we would also let Awesome Miner use the NetHash formula if for example the coin Difficulty is zero. Have you had a chance to test if this formula gives accurate numbers?
CoinsPerDay = hashRate / (hashRate + nethash) * secondsPerDay / blocktime * reward

3) Today you can only set Profit Factor for a Coin over the API, but not for a pool. If it's needed for pools as well it should be easy to add.

Hi Patrike,

I haven't tested the "accuracy" of the formula cause luck is also a factor + I used autoexchange on ZergPool which made it a little hard to track earnings, but it was what I was using for the past 2 days for experiment. (see pic)

https://imgur.com/HBOVlmx

so from the picture, you can see I'd need to add my own BlockTime where AM's API reported 0 due to coin providers, then some factors I consider important as below.

* The NetHash has to be accurate, cause else it'll affect the entire calculation as per the formula we discussed here
* BlockWorth for solo as some blockchains block reward just won't cover the cost even if you win 100% of blocks even the difficulty was low etc. This this is filtered to suit one's need (for me, 500 satoshis per minute)
* BlockWinChance, Simply used the hashRate / (hashRate + netHash) to work out percent chance I'm likely to hit a block
* BlockWin_IntervalSec, to keep consistent flow of earnings a big win every few days/weeks may not be as good as lots of little wins daily
* SatPerMinute, Just for earning reference in perfect fair conditions (not sure I used the terminologies correct at all, but you get the idea)
* Division <--- now, this is something I'm trying to find a way to prioritize pools with a balancing factor but like I have mentioned, my maths are bad so I don't even know if this is right (currently using SatPerMinute / BlockWin_IntervalSec).

Result for the past 2 weeks follows, AM estimate on earnings are averaging about 40 USD or more, I tried solo mining, conventional shared mining, switching interval of 5~10minutes. regardless, I'm only averaging about 200 satoshis per minute, which is far from the earnings estimate regardless of which formula I used, call it a streaks of bad lucks, but even shared mining didn't end up much better, the Yiimp pools (used Zerg, zPool mainly) tend to seem to have particularly bad lucks that usually sees block efforts 500% regardless solo/shared mining.

This is to report on the effect of the Dynamic Coin Properties Update on earnings I promised 2 weeks ago since it was made available.

Now it's only been 24 hours since I used the Excel custom profit factoring to prioritise pool, so I cannot say this is going to continue but so far I'm seeing vast improvements on earnings (doing solo mode on most chains where feasible for my farm's hashrate on ZergPool with AutoExchange), I'm averaging approx 400 satoshis per minute which is about double of what I get for the past 2 weeks via various methods as described above.

***

So if this works out, you might consider some similar sort of mathematically correct feature to implement some kind of profit factors based on the above metrics (since they are already all available in AM) similar to how you apply factors for Online Services vs Actual/Estimated earnings, I believe this will be then be a lot closer to SMART profit switching, more likely better than what NPLUS Miner's claimed PLUS logic ;p

***
3) Currently I worked around the need to apply pool profit factors by using the API to include the top 3 pools in the Excel List I showed here in my example, so ability to modify pool profit factor via API is not that much sought after anymore, since there are also benefits for a small selection of profitable pools to mine for, as some of my hardwares are low memory (1060 3GB) and they won't work on many of the new algos such as MTP, GRIN...etc.

Best Regards,

[powerstr]

Hello!
Tell me how to set up dual mining ETH + MAX?
-esm 2 -allpools 1 -allcoins 1 -dpool hub.miningpoolhub.com:20461 -dwal xxxx -dpsw xxxx -dcoin keccak -r 1 -dbg -1 -retrydelay 3 -dcri 5 -tt 72 -ttli 79 -tstop 82 -fanmin 50
It does not help me!

[patrike]

Hey Patrik,

in the benchmark you can only bench 1 card at a time or all together. Is it possible to change this to multiple selectable cards, like bench with just the cards number 2, 4, 5 and 8?

Maybe with a selectable mark at the left side and two buttons "Select All" and "Select None" at the bottom. But if so, please select all cards as the pre-filled standard.

This would be awesome for multiple cards rigs to bench just specific cards together.

Hello. In most scenarios it's better to benchmark a single GPU and save it to a Profit Profile. You can then use Profile Groups to create combinations of GPU's if needed, for example one nVidia 1070 + two nVidia 1080. As long as you have similar cards in terms of clockng across many miners, you can then reuse the same results across many miners.

In you case, are these cards all the same or a mix?

Hey Patrik,

its mixed. Different brands, different models, different clocks. So it makes no sense to bench a single card and just multiple it or something similar. Benching a few cards together to run them in one profile, and benching other cards together to run in a different profile, and so on, is the idea behind. But maybe someday you find this idea great too and implement it

I've made a number of internal updates for the GPU selection recently, to make it better at mapping the actual selection to what the mining softare expects. There are a number of different ways the mining software order the GPU's, so it's not as easy like GPU 3 is number 3 when passed to the mining software.

I'm about to finalize the improved devices selection for the next development release and this will make it possible to better support benchmarking of multiple GPU's as well. I'm planning to have it ready soon - can you please test once available?

[patrike]

@patrike - Can you add an option (in miner properties) to use average hash rate to calculate profit instead of 5s hash rate? Some miners have wild fluctuations in 5s rate, which does not give right figures.

Thanks for the suggestion. Is this specifically with ASIC miners in mind where they report their own average hash rates? Most GPU mining software only report the current value, so in that case Awesome Miner would have to calculate the average over a period of time.

Yes, it’s for ASICs like Zig Z1, Antminer Z9, Antminer B7 etc.

Thanks for the update.

I will look into this as it's only the display of revenue/profit on the dashboard/miners tab that should be affected, while the revenue history still must be based on the 5s values to generate a realistic summary.