Hi, it actually makes sense to have benchmarks per coin instead of per algo. It may be a bit of hard work to tweak this in the programming, but in the long run us (users) will have a more down to earth expectation of what we would be earning and the profit switching would be more accurate.
I'm not sure why you would want this. Awesome Miner calculates your earnings based upon your current hashrate, and current price price/difficulty of the coin.
If you are getting a different hashrate for two coins on the same algorithm, then something is wrong with you system or setup.
I think you do not pay much attention to hashrates for hours like me.
Choose 10 different coins, for example Neoscrypt, from different pools in different parts of the world, and then take the test. You'll see that you get different hashrate values.
If I am in Spain and I am in contact with a server in the USA or Japan, my connectivity is not as good, with which the hashrate is reduced. If the configuration of Vardiff is not correct in the server, it also changes the hashrate, and so several more things. Hypothetically it is always the same hashrate, but different causes make it fall for different reasons. A Pool in a bad server, will have bad connectivity, bad response, and therefore a poorer hashrate.
I think you are introducing artificial problems here. The hashrate on the pool side may be different, but it will be the same on your rig for the same algorithm if every other setting is equal.
I don't understand why you would intentionally connect to pools that would introduce more latency.
The only way to get it right and correct is to be able to measure the hashrate by pool / currency
But this would be an inaccurate measurement by Awesome Miner. Awesome Miner can't control the packets as they travel across the internet. You could be affected by natural latency, by bad routing by ISPs and carriers.
I only invite you to take the test and then give your opinion. I have seen it in many currencies, in X17, x16s etc ... Different currencies, different hashrates, but within a margin. In X17 XVG the same rig gives 114-118 mhs, and in another currency that I can not remember now it did not exceed 105, and it is the same thing.
These hashrate differences cause the switch to be incorrect.
This is forcing me to do 3 hours tests in each pool / currency to see the deviation and modify it in the pool through the Profit field, but this is just a patch.
Please do the test and then give your opinion.
I honestly think you are making this harder than it should be. You should be selecting low latency pools.