Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MRR Prices #1131

Closed
acos0874 opened this issue Aug 12, 2020 · 9 comments
Closed

MRR Prices #1131

acos0874 opened this issue Aug 12, 2020 · 9 comments
Assignees

Comments

@acos0874
Copy link

Please can you help me to understand how MRR prices are set? I am using profit factor 1.4 but I seem to keep getting rentals at lower than nicehash is paying just on ethash and just on one of my rigs.

@acos0874
Copy link
Author

Actually I just realised I can set a higher price modifier for ethash than other algos.

@RainbowMiner
Copy link
Owner

RainbowMiner commented Aug 13, 2020

Yes, that's right - the problem might be related to an averaging effect. The ETH prices paid on Nicehash have been rising very fast, the past days. So the rig's average income average might lag behind. That is especially true, if your rig is rented out most of the times.
You might want to delete all "Profit-GPU*.txt" files in Stats directory (not the subdirectories). It then takes three hours of normal mining, until a new average is reached.
Actually, this thing highlights one problem of the profit tracking (it only tracks during normal profit switching operation). I am thinking about a way to track the profitability, even when rented out.

@acos0874
Copy link
Author

I just realised a work around in these situations is to use +xx% auto price modifier for nicehash in particular. It might be worth using a -xx% for non-nicehash algos to capture more rentals.

@acos0874
Copy link
Author

If a permanent fix is a while away, would it be possible to implement a pause between rentals? For example, when one rig completes, the rig can't be rented again for 3 hours? Maybe the average and pause time could be customised.

@RainbowMiner
Copy link
Owner

Yes, that's a very good idea. It turned out to be pretty complicated, to have kind of a background profitability monitor running. So, adding some pause (maybe for an hour) and interpolating a bit could solve the problem pretty easy. I'll try that one.

RainbowMiner added a commit that referenced this issue Aug 18, 2020
- disable MRR for devices/workers that need benchmarking
- trigger MRR update immediatly after one device/worker has finished benchmarking
- eventually solve issue #1131
@acos0874
Copy link
Author

Is it also possible that the mrr data file can become corrupt? I have had a couple of rentals today at lower than nicehash-ethash and the prices have been pretty stable.

@RainbowMiner
Copy link
Owner

This commit f1f5db0 eventually solves this problem.

@RainbowMiner
Copy link
Owner

I have updated the miningrigrentals code, so that there will be no more need to have all those pools activated after they have been used for benchmarks. The hashrate and powerdraw will be stored in a cache. If this cache is disrupted, the new code uses the advertised hashrate on MiningRigRentals to recalculate the minimum price, thus following your rig's profitability.

@RainbowMiner
Copy link
Owner

RainbowMiner commented Aug 27, 2020

Awkward as it is - yes, currently we need to activate all pools at first. I am working an a solution for that. It's a non-trivial task, though.

Correction: not all, but some. You get the best results by activating MoneroOcean,Nicehash,Zergpool,Zpool

For MoneroOcean, you will have to set a XMR wallet in pools.config.txt, the others automatically use your BTC address (for Nicehash use the internal mining wallet address specific to your Nicehash account).
If you do not want to have anything to do with XMR, please feel free to use my XMR wallet:
8966CzKtSdaHvEUccMbWiUTrdCcuqHngrbZ8P2CsfjBTUCfTzoiY5RhBu8sK3RzYFGbyy45qL8utzadY4qNsKCAB7vNREYT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants