could be also relevant for you nostr:nprofile1q9z8wue69uhk77r5wfjx2anpwcmrg73kx3ukydmcxeex5ee5de685ut2dpjkgmf4vg6h56n3w4k82emtde585u35xeh8jvn3vfskgtn0de5k7m30q9z8wue69uhhyetvv9unwmt9x46hw7r0wehxcet9ddukv6m9xe6nwmr6w3hngumzv95x7unfxdnkuet8vd6nvdm80f3hgmt4vaskgtn0de5k7m30qqszrsd9y5r2xs739s6vpfp57lrvmgnk5cy7u5dq5qjn8l4lpjz0kwsdku3e8

Reply to this note

Please Login to reply.

Discussion

Oh, that's interesting. πŸ‘€

But that would mean I had to run xmrig myself. That's something I had to figure out first.

maybe these settings can be set in your setup manually.

maybe google first what your CPU "should" be capable of in terms of hashrate. if it's 50% off, then you might be able to tweak with settings.

Good idea.πŸ‘

And that's something I could potentially achieveπŸ˜‚

If you're using Gupax(x), you can specify commands for xmrig if you set it to advanced.

Maybe that works.

Those commands did nothing for me under Arch (running through Gupax). I think Gupax(x) already applies certain optimizations, possibly including these.

If you already tried the commands in the GUI, I don't think it makes a difference on an other distro.

I thought it could be in a config file and not in the GUI. When I feel the need and have time I'll have a closer look.