-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
About the NO_WARMUP and NO_AFFINITY options in Makefile.rule #439
Comments
@jgpallero WARMUP has no or a negative effect on newer machines with processors for AMD. The performance difference is the result of very comprehensive testing, that showed that some |
closed this issue |
@wernsaar Thank you very much for your answer. About the benchmarks, last year I wrote a small program to do some tests using (S|D)GEMM, (S|D)TRMM and (S|D)SYRK from BLAS and (S|D)GETRF and (S|D)GEQRF from Lapack. Some plots are created using matplotlib. The code is here: https://bitbucket.org/jgpallero/pblb |
On 27.08.2014 11:26, jgpallero wrote:
Thank you. I will look at the codes. Best regards |
Hello:
Inspecting the 0.2.11 and the old 0.2.8 OpenBLAS versions I've noted that the NO_WARMUP and NO_AFFINITY options in Makefile.rule have not the same values. In OpenBLAS 0.2.8 both are commented in the Makefile.rule:
NO_WARMUP = 1
NO_AFFINITY = 1
but in the new 0.2.11 they are activated as:
NO_WARMUP = 1
NO_AFFINITY = 1
I remember some comments in the mailing list or here in the issues section related to differences in performance between versions and I remember also someone said that it could updated using these variables.
Why the variables are uncommented in the Makefile.rule in recent OpenBLAS versions?
The text was updated successfully, but these errors were encountered: