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

Feature request: Display CPU model #80

Open
disconsented opened this issue Sep 18, 2019 · 6 comments
Open

Feature request: Display CPU model #80

disconsented opened this issue Sep 18, 2019 · 6 comments

Comments

@disconsented
Copy link

Frequently performance issues are cause by anemic hardware,
being able to display the CPU model along side some other metrics like cores available to the JVM, enabled mitigations and current clocks would go a long way helping diagnose this.

@electronicboy
Copy link

I did consider looking into this a while back, ended up not persuing it as I was somewhat offput by the idea of having to chunk something like oshi into paper (https://github.com/oshi/oshi) and co

@disconsented
Copy link
Author

For the short term, what about querying a few things like lscpu?

@Joo200
Copy link

Joo200 commented Sep 20, 2019

lscpu is a unix command. That doesn't work for windows.
There should be a platform independently solution for this.

@disconsented
Copy link
Author

I never said use lscpu only, I said use things like lscpu.

With powershell you can do Get-WmiObject –class Win32_processor | select * which outputs something similar.

Of particular note from lscpu:

  • NUMA nodes
  • Sockets
  • Model/Model name
  • Cache
  • CPU(s)
  • CPU MHz

This should cover most use cases and provide enough useful information into how resources are allocated to whatever (virtualised) environment MC is being ran in. Querying Runtime.getRuntime() should be considered more powerful here for what its worth.

Additionally, querying lspci and filtering for Network controller, SATA Controller and Non-Volatile memory controller should provide enough information about storage models.

What are your thoughts on this @electronicboy ?

@electronicboy
Copy link

Throwing in oshi would be a much better solution vs tryna deal with parsing that mess ourselves

@disconsented
Copy link
Author

disconsented commented Sep 23, 2019

Up to you, just providing an alternative

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