Quote from: dudel42 on January 22, 2018, 09:23:45 PM

Quote from: FonsecaMinesLLC on January 22, 2018, 08:02:50 PM

Quote from: dudel42 on January 22, 2018, 04:01:08 PM

I see a problem with the recently added always updating "benchmark" results: when you add or remove GPUs after you've done the benchmarks the results get messed up, as the currently running algos will change in values, whereas others will not. especially when adding GPUs this will move the current top algo(s) up ahead above the others so they never run again and therefore also don't update their results.

maybe an option to disable the updating after benchmarks could be added?

I think a better solution would be to delete your current benchmarks and re-bench everything when you make a hardware change.. That way you would have the most up to date accurate info out there...

in principle yes -- but since accurate benchmarking takes like 6 hours this is not a practical solution. I'm not talking about major architecture changes (like adding new/different GPU types), but simply adding or removing a card of the same type -- so hashing speed simply scales over all algos.

since obtaining GPUs for reasonable prices is extremely difficult now I'm simply adding them when I get them. so a rig running (and benchmarked) with three 1070ti might get another 1070ti added once a week until the rig is full. re-running the benchmarks every time is just not practical and also a loss of profits.

Ok, so if you are frequently adding cards of the same types, and are expecting the same hash rate, then just go in and manually adjust the benchmarks yourself when you add a new card. Then MM will update the hash rate to more accurately reflect the actual performance of the cards as the algos are called (since we all know that the same cards can have +/-10% performance depending on the silicon lottery).