Partial #performance comparison of #blas / #lapack in #rstats using Xeon E5-2697, i3-12100t, Ultra 7, 265, i7-11000 . The old timer still punches well for its age. Interesting to watch the less than gracious degradation in the AVX512 capable chip (i7)
The plot thickens #BLAS #rstats #lapack
(When one is about to rip through 10s of millions of medical records, one must profile the tools if the project is to finish before one's retirement)
FlexiBLAS makes this benchmarks a breeze
The plot thickens #BLAS #rstats #lapack (When one is about to rip through 10s of millions of medical records, one must profile the tools if the project is to finish before one's retirement) FlexiBLAS makes this benchmarks a breeze
The plot thickens #BLAS #rstats #lapack
(When one is about to rip through 10s of millions of medical records, one must profile the tools if the project is to finish before one's retirement)
FlexiBLAS makes this benchmarks a breeze
I wonder if the #lapack that comes with #AOCL is being picked up by flexiblas in #rstats. The things I have to do for the love of electronic health records analytics #bigdata #blas
The plot thickens #BLAS #rstats #lapack
(When one is about to rip through 10s of millions of medical records, one must profile the tools if the project is to finish before one's retirement)
FlexiBLAS makes this benchmarks a breeze
I wonder if the #lapack that comes with #AOCL is being picked up by flexiblas in #rstats.
The things I have to do for the love of electronic health records analytics #bigdata #blas
I wonder if the #lapack that comes with #AOCL is being picked up by flexiblas in #rstats.
The things I have to do for the love of electronic health records analytics #bigdata #blas
I wonder if the #lapack that comes with #AOCL is being picked up by flexiblas in #rstats.
The things I have to do for the love of electronic health records analytics #bigdata #blas
LFortran compiles LAPACK

Every respectable Fortran compiler must be able to compile LAPACK, probably the most famous and influential Fortran library. Christopher Albert spent most of December 2025 to get it working, it took about 70 PRs (pull requests). For context, LFortran is composed of about 4,500 merged PRs at GitHub plus another 1,800 merged PRs at GitLab (before we switched to GitHub), total of 6,300 PRs. So 70 PRs is about 1% of all the PRs, very impressive effort!

LFortran