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

Experiment with Processor Topology/Affinity/Pinning #373

Open
haesbaert opened this issue Jul 12, 2022 · 2 comments
Open

Experiment with Processor Topology/Affinity/Pinning #373

haesbaert opened this issue Jul 12, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@haesbaert
Copy link

I've recently released https://github.com/haesbaert/ocaml-processor which exposes the processor topology and allows for pinning of processes/domains to a set of cpus.

There were some discussions in Paris concerning which tests are affected more/less by the presence of hyper-threading and/or sockets and other NUMA artifacts.

Using ocaml-processor might expose some performance properties of different benchmarks when the affinity is changed, as in:
"What happens with test X when I restrict socket count, or isolate hyper-threading".

I'm obviously available for any help needed with the setup.

ccing @Sudha247 who suggested opening an issue.

@shakthimaan
Copy link
Contributor

At present, the .bench file produced by Sandmark has a header entry with kernel, version and CPU architecture information. The ocaml-processor library will be useful to augment the meta-data. Thanks for filing the enhancement request.

@shakthimaan shakthimaan added the enhancement New feature or request label Jul 12, 2022
@haesbaert
Copy link
Author

At present, the .bench file produced by Sandmark has a header entry with kernel, version and CPU architecture information. The ocaml-processor library will be useful to augment the meta-data. Thanks for filing the enhancement request.

Awesome !

I think it could also be useful to see how dual socket machines perform if you restrict sockets, or what happens with tests if you don't use hyper-threading as well

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

No branches or pull requests

2 participants