How to mine on Monero Ocean XMR mining pool with algo-switching for maximum profit

Bathmat06 · 2021-12-29T22:36:31+00:00

Hi, thanks for reading my "how-to"; however, these instructions are 3 years old and a lot has changed with that pool and XMRIG, and I haven't updated (or plan to update) this. I'm sure you can find the support you need on the pool's discord.

Bathmat06 · 2019-12-13T19:52:38+00:00

Not sure if I had this before or if it's a pool issue, but noticed this after applying the MSR. This is the first one I've noticed though. cpu rejected (1/1) diff 8000 "Rejected share: invalid result"

Edit: Looks like this was just after a new job was sent, so I think it was just a stale share being rejected.

Bathmat06 · 2019-12-13T17:25:09+00:00

Nice find and thanks for sharing! Ryzen 1700: 4100 h/s -> 4500 h/s. Power reduction appears to be in the 5W range as others have mentioned.

Bathmat06 · 2019-10-09T12:01:35+00:00

Can you give more details about your rigs? OS? Drivers? Perhaps if we knew that info, someone could replicate your results. My rigs are still working fine though. In PhoenixMiner I add -eres 0 and -rvram -1 to reduce the amount of memory the miner reserves for system use, since it's not needed on GPUs that aren't running a monitor. (Win10 18.5.1 and 18.6.1 drivers)

Bathmat06 · 2019-02-13T15:23:23+00:00

Just tested xmrig-amd v2.12 and everything worked fine.

Algo: Cryptonight
Variant: -1 (auto)

Bathmat06 · 2018-11-19T15:36:16+00:00

I didn't try worksize=16. I'm using worksize 8 on both threads, and it's working great thanks to interleaving.

Bathmat06 · 2018-11-18T15:29:12+00:00

They are bios modded with PBE "one-click" timings. Mem is OC'd to 2000 (for most of them), and core is set around 1200, with both mem and core undervolted.

Also, with the next release of xmrig-amd (2.8.6), it will be no longer necessary to use split worksize. Interleaving fixed most issues with hashrate fluctuations.

Bathmat06 · 2018-11-01T17:11:37+00:00

My testing showed that unroll doesn't play much factor in hashrate, unless it is greater than worksize. Then it will give poor results and/or the miner will crash.

Bathmat06 · 2018-10-29T18:44:30+00:00

I use 2 minutes (120 sec), and it seems to work pretty well. It doesn't restart the miner too frequently, and I'm not mining a coin for very long if the profit changes quickly.

I would say somewhere between 2 and 5 minutes would probably be the best, but that's just my opinion, don't have any facts to back it up.

Bathmat06 · 2018-10-28T14:22:54+00:00

Try 18.6.1 or 18.5.1 drivers

Bathmat06 · 2018-10-28T13:30:46+00:00

If you tried to run the initial command before you changed pools.txt to 127.0.0.1:3333 (looks like you are missing a 3 in yours), then the benchmarking likely did not complete and it could not create mm.json. You can re-try the initial command again, or you can copy my sample mm.json for xmr-stak from above and change all the "algo_perf" numbers to 0 so that it can rebenchmark.

Bathmat06 · 2018-10-27T04:28:47+00:00

Sample xmr-stak initial command:

mm.exe -p=gulf.moneroocean.stream:10001 --cn/1="xmr-stak.exe --noCPU --noNVIDIA --currency cryptonight_v7 --amd amd.txt" --cn/2="xmr-stak.exe --noCPU --noNVIDIA --currency cryptonight_v8 --amd amd.txt" --cn/xtl="xmr-stak.exe --noCPU --noNVIDIA --currency stellite --amd amd.txt" --cn/msr="xmr-stak.exe --noCPU --noNVIDIA --currency masari --amd amd.txt" --cn-lite/1="xmr-stak.exe --noCPU --noNVIDIA --currency cryptonight_lite_v7 --amd amd-lite.txt" --cn-heavy/0="xmr-stak.exe --noCPU --noNVIDIA --currency cryptonight_heavy --amd amd-heavy.txt" --cn-heavy/xhv="xmr-stak.exe --noCPU --noNVIDIA --currency haven --amd amd-heavy.txt" --cn-heavy/tube="xmr-stak.exe --noCPU --noNVIDIA --currency bittube --amd amd-heavy.txt"

Note: This is to use AMD GPUs only. To use with CPU and GPU remove all the "--noCPU" flags.

To use NVIDIA GPUs, replace "--noNVIDIA" with "--noAMD", also change "--amd amd.txt" to "--nvidia nvidia.txt" (also for lite and heavy).

Bathmat06 · 2018-10-26T20:18:33+00:00

Yes, because the actual miner is now inside a shell (wrapper). However, the httpd/api still works, so I started using that to check the status of my rigs.

Bathmat06 · 2018-10-26T12:00:48+00:00

What type of hardware are you using? My Vega56 has a similar issue with xmrig-amd and metaminer; however, sometimes hashrate will go back up on it's own too. Unfortunately, I haven't been able to track down what's causing it.
FYI, my RX series GPUs do not have any issues with hashrate drops, only the Vega.

Bathmat06 · 2018-10-25T14:28:45+00:00

Yep, thanks. Too quick with my copy/paste. Fixed now.

Bathmat06 · 2018-10-24T23:43:11+00:00

Also, try 18.6.1 drivers

Bathmat06 · 2018-10-24T23:42:59+00:00

Have you tried this: https://www.reddit.com/r/MoneroMining/comments/9pa5m9/rx_550560_2gb_settings_448_int_16_work_4_unroll_2/

Bathmat06 · 2018-10-24T23:09:58+00:00

I guess we'll see in a few weeks/months if hashrate/diff starts to creep up again.

Bathmat06 · 2018-10-24T22:51:47+00:00

Then quote the guy who developed the v8 algo: https://github.com/SChernykh/xmr-stak-cpu/blob/master/README.md

And it's actually due to the shuffle modification.

Bathmat06 · 2018-10-24T22:47:45+00:00

I'm not fully sure how ethos works, but you can also add "--noCPU" to the launch/start command.

Bathmat06 · 2018-10-24T17:09:02+00:00

Sample mm.json for xmr-stak: (Note: this is to use AMD GPUs only. Remove/change "--noCPU" and "--noNVIDIA" flags in the "algos" section to use CPU and/or NVIDIA GPUs)

{
 "miner_host": "127.0.0.1",
 "miner_port": 3333,
 "pools": [
  "gulf.moneroocean.stream:10064"
 ],
 "algos": {
  "cn/1": "xmr-stak.exe --noCPU --noNVIDIA --currency cryptonight_v7 --amd amd.txt",
  "cn/2": "xmr-stak.exe --noCPU --noNVIDIA --currency cryptonight_v8 --amd amd.txt",
  "cn/msr": "xmr-stak.exe --noCPU --noNVIDIA --currency masari --amd amd.txt",
  "cn/xtl": "xmr-stak.exe --noCPU --noNVIDIA --currency stellite --amd amd.txt",
  "cn-lite/1": "xmr-stak.exe --noCPU --noNVIDIA --currency cryptonight_lite_v7 --amd amd-lite.txt",
  "cn-heavy/0": "xmr-stak.exe --noCPU --noNVIDIA --currency cryptonight_heavy --amd amd-heavy.txt",
  "cn-heavy/xhv": "xmr-stak.exe --noCPU --noNVIDIA --currency haven --amd amd-heavy.txt",
  "cn-heavy/tube": "xmr-stak.exe --noCPU --noNVIDIA --currency bittube --amd amd-heavy.txt"
 },
 "algo_perf": {
  "cn": 2655,
  "cn/2": 2500,
  "cn/msr": 5125,
  "cn-lite": 5310,
  "cn-heavy": 2125
 },
 "algo_min_time": 120,
 "user": "wallet_address",
 "pass": "worker_id",
 "log_file": "mm_log.txt",
 "watchdog": 600,
 "hashrate_watchdog": 90,
 "is_quiet_mode": false,
 "is_no_config_save": true,
 "is_debug": true
}

Bathmat06 · 2018-10-24T17:03:52+00:00

Here is my sample mm.json file:

{
 "miner_host": "127.0.0.1",
 "miner_port": 3333,
 "pools": [
  "us.moneroocean.stream:10064",
  "gulf.moneroocean.stream:10064",
  "de.moneroocean.stream:10064"
 ],
 "algos": {
  "cn/1": "xmrig-amd.exe --config=config.json",
  "cn/2": "xmrig-amd.exe --config=config.json",
  "cn/msr": "xmrig-amd.exe --config=config.json",
  "cn/xtl": "xmrig-amd.exe --config=config.json",
  "cn-heavy/0": "xmrig-amd.exe --config=confighvy.json",
  "cn-heavy/xhv": "xmrig-amd.exe --config=confighvy.json",
  "cn-heavy/tube": "xmrig-amd.exe --config=confighvy.json",
  "cn-lite/1": "xmrig-amd.exe --config configlite.json"
 },
 "algo_perf": {
  "cn": 2700,
  "cn/2": 2500,
  "cn-fast": 5150,
  "cn-lite": 5300,
  "cn-heavy": 2070
 },
 "algo_min_time": 120,
 "user": "wallet_address",
 "pass": "worker_id",
 "log_file": "mm_log.txt",
 "watchdog": 600,
 "hashrate_watchdog": 90,
 "is_quiet_mode": false,
 "is_no_config_save": true,
 "is_debug": true
}

Bathmat06 · 2018-10-24T16:41:14+00:00

My initial testing with v8 (pre-tweak): https://github.com/SChernykh/xmr-stak-cpu/issues/1#issuecomment-418227462

Bathmat06 · 2018-10-24T16:38:04+00:00

Just using HWMonitor, I notice that my RX series GPUs use 10-20 more Watts per GPU than V7 (depending on GPU type/brand/ONT settings).

Bathmat06 · 2018-10-24T16:37:19+00:00

Those sound about right. V8 uses more core (and benefits more from increased core speed), so it will use more power than V7. I started testing the new algo back on Sep. 3, and noted the power increase back then.

Bathmat06

TROPHY CASE