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

[2.1.0] threads and max-cpu-usage is not working #274

Closed
agisubagio opened this issue Oct 29, 2019 · 2 comments
Closed

[2.1.0] threads and max-cpu-usage is not working #274

agisubagio opened this issue Oct 29, 2019 · 2 comments

Comments

@agisubagio
Copy link

agisubagio commented Oct 29, 2019

I can not use threads and max-cpu-usage with the latest release. I think you should update this wiki page https://github.com/Bendr0id/xmrigCC/wiki/Config-XMRigDaemon

...cut...
},
"donate-level": 1,
"donate-over-proxy": 0,
"log-file": null,
"threads": 4,
"max-cpu-usage": 50,
"pools": [
{
...cut...

result:

  • ABOUT XMRigCC/2.1.0 MSVC/2017 (RELEASE)
  • LIBS libuv/1.31.0 OpenSSL/1.1.1c hwloc/2.0.4
  • HUGE PAGES permission granted
  • CPU Intel(R) Xeon(R) CPU E5335 @ 2.00GHz (2) x64 -AES
    L2:16.0 MB L3:0.0 MB 8C/8T NUMA:1
  • DONATE 1%
  • ASSEMBLY auto:none
  • POOL Fixed windows build #1 172.16.200.20:4441 algo auto
  • COMMANDS hashrate, pause, resume
  • CC Server 172.16.200.20:8080
    [2019-10-29 07:53:03.769] use pool 172.16.200.20:4441 172.16.200.20
    [2019-10-29 07:53:03.770] new job from 172.16.200.20:4441 diff 10000 algo cn/r height 342452
    [2019-10-29 07:53:03.770] cpu use profile cn (8 threads) scratchpad 2048 KB
    [2019-10-29 07:53:06.558] cpu READY threads 8(8) huge pages 8/8 100% memory 16384 KB (2789 ms)
    [2019-10-29 07:54:05.474] speed 10s/60s/15m 95.4 n/a n/a H/s max 96.3 H/s
    [2019-10-29 07:54:43.903] [CC-Client] Command: UPDATE_CONFIG received -> update config
    [2019-10-29 07:54:43.921] [CC-Client] Config updated. -> reload
@electroape
Copy link

Yes, 2+ uses new XMRig CPU config : https://github.com/xmrig/xmrig/blob/master/doc/CPU.md
Config overall is largely different, you should've seen a large block of CPU threads definitions for several algos which it writes by default if "autosave" is true. You can disable autosave and define
"*": {
"threads": X,
"intensity": 1,
}
To un-litter the config.

@Bendr0id
Copy link
Owner

Updated the wiki

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

No branches or pull requests

3 participants