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

How to change intensity and worksize in v5.0.1? #1322

Closed
wisnia37 opened this issue Nov 27, 2019 · 4 comments · May be fixed by #3475
Closed

How to change intensity and worksize in v5.0.1? #1322

wisnia37 opened this issue Nov 27, 2019 · 4 comments · May be fixed by #3475

Comments

@wisnia37
Copy link

How do you change these parameters in the latest version to bypass the default settings for the NVIDIA card?

@username1565
Copy link

Hello. Can you add argument --intensity, or "intensity":value in JSON-config,
to set intensity of mining on each core, and decrease this intensity, using trottling, or some delay?
Because limitation of number of the CPU-threads, decreasing usage of CPU-cores,
but loading on this corea is 100%, and temperatures is maximum, on each loaded CPU-core.
Not good...
What if need to load 8 cores up to 25%, and no more?

Thanks.

@Spudz76
Copy link
Contributor

Spudz76 commented Dec 4, 2020

@wisnia37 CUDA doesn't use intensity or worksize you're thinking of OpenCL. As the autoconfig for CUDA is generated inside the xmrig-cuda plugin there are no commandline options for threads/blocks, and the ones for bfactor/bsleep don't seem to work either:

      --cuda-bfactor-hint=N     bfactor hint for autoconfig (0-12)
      --cuda-bsleep-hint=N      bsleep hint for autoconfig

So then let it generate the highest possible threads/blocks and turn them down (and/or add bsleep/bfactor) by hand.


@username1565 Repaste your heatsinks if you can't run 100% 24/7 without hitting thermal throttling.

25% would be running autoconfig once for a "full" setup and then go in and delete 75% of the threads in some balanced way.

There is an option for this (--cpu-max-threads-hint=N maximum CPU threads count (in percentage) hint for autoconfig ) but I've never had it work right, therefore I just let it calculate 100% and then carve it away by hand.

@username1565
Copy link

username1565 commented Dec 9, 2020

@Spudz76, yes, now I using threads:2 in algo config-section, instead of --cpu-max-threads-hint=N, and I see 2 cores from 8 was been loaded. But this is loaded up to 100% and temperatures there about 100 celsium.
I just wanted to use something, like --max-cpu-usage=25 to set 25% of loading for each core, and do not see so high temperatures, on each core. Maybe there is possible to use trottling, or time delays, to implement this.

@xmrig xmrig closed this as completed Apr 12, 2021
@James4Ever0
Copy link

James4Ever0 commented May 3, 2024

Turned out it is straightforward to slow down the mining process, by adding some sleep code here:

xmrig::Job xmrig::Miner::job() const
{
    std::lock_guard<std::mutex> lock(mutex);

    return d_ptr->job;
}

I will make a pull request ASAP.

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

Successfully merging a pull request may close this issue.

5 participants