Command recipes and M1 Max optimization

Chainfire / UselethMiner

Ethereum CPU miner and aggregating proxy

87 stars 7 forks source link

Command recipes and M1 Max optimization #12

Open BenRacicot opened 2 years ago

BenRacicot commented 2 years ago

Hello and thank you for this incredible project. I wanted to ask for clarification on command recipes for Apple Silicon.

The command I've settled on: /usr/local/uselethminer/uselethminer 0x07D91907b1F0F78591C2E3291ed87E465Bd1Eaa8.eth-us-east1@nanopool.org:9433 -t 10 -fg metal -f armv8af

Idles like below while CPU/GPU are not being used according to benchmarks. What am I missing?

UselethMiner v0.23
[SYSTEM] Apple M1 Max, 10 threads, arm64, 64 GB RAM
[CFETHASH][CPU] Selecting: ARMv8A (Full) (from commandline)
[CFETHASH][GPU] Selecting: Metal (from commandline)
[CONTROLLER][RPC] Listening on 127.0.0.1:3326

Perhaps it's the mining pool? But thought I'd ask for advice here.

Also, should we be specifying thread counts or will the UselethMiner leverage as many as possible automatically? (I noticed Arm is said to be 64 but the M1 instructions have size set to 88.)

Chainfire commented 2 years ago

I'm not sure why it sometimes does this. I've seen it happen during testing once in a while too. Might well be a connection issue, try a different pool.

As for threads, you already specified threads with -t 10, which is the most you should use on an M1 Max. The --size 88 parameter refers to an internal block size, changing that one up does influence performance, it is 64 by default on ARM.

BenRacicot commented 2 years ago

Wow strange! Thank you for the reply. I see you use ViaBTC. The same issue happens there too. I can't seem to get it to mine.

USERNAME.stratum+tcp://eth@viabtc.io:3333 -f armv8af -s 88 -fg metal

Also, anything I can help with?

Chainfire commented 2 years ago

ViaBTC is a little messy since their DNS issues two months ago... I use this format:

/usr/local/uselethminer/uselethminer USERNAME.WORKER@eth.viabtc.top:3333 -f armv8af -s 88 -t 10 -fg metal

Not sure what your connection string was supposed to be but it was definitely wrong 😂

EDIT: Actually now I look at your original post that connection string cannot possibly be right either...

BenRacicot commented 2 years ago

Haha, I'm not sure but the above doesnt work either. It did help though!

USERNAME@eth.viabtc.top:3333 works Thanks for sharing your working version because ViaBTC doesnt give that address anywhere I can find. instead they show stratum+tcp://eth.viabtc.io:3333 which does not connect in any form.

Also you included WORKER which I omitted. Not sure what that is. I can now report ~20Mh/s with the same MBPM specs you have :)

Taffjones commented 2 years ago

Same issue unfortunately. Tried with two different pools

e.g. /usr/local/uselethminer/uselethminer 0xWALLET_ADDRESS_HEX.test2:x@eth.hiveon.com:4444 -fg metal -f armv8af -m