-
-
Notifications
You must be signed in to change notification settings - Fork 947
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
Better support for asymmetric CPU cores #2557
Comments
We already support
If that's true, that would be an issue for runtime or the OS, not BDN. |
Is there more handy way to compare different affinities? |
I don't think there is another built-in way to do it. You could create your own attribute to do it, though. [AttributeUsage(AttributeTargets.Class | AttributeTargets.Assembly, AllowMultiple = true)]
public class AffinitizedJobAttribute : JobConfigBaseAttribute
{
// Add whatever other settings you need.
public AffinitizedJobAttribute(int affinity) : base(Job.Default.WithAffinity((IntPtr) affinity)) { }
} |
I don't think there is anything actionable here, so closing this out. Let me know if you disagree. |
When running benchmark on my Raptor Lake processor, I find the time of each iteration shifts between two values if I switch the console window to background.
This is probably due to the "smart" scheduling for P/E cores of Windows. I've also heard that thread affinity API getting ignored by the system in some situations.
It would also be interesting to see the results on E-cores. To be more general, there can be a configuration to set thread affinity for benchmarks. This can also help benchmarking for arbitrary core counts.
The text was updated successfully, but these errors were encountered: