home.social

#blas — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #blas, aggregated by home.social.

fetched live
  1. Микроядро SME2 sgemm: 1024 умножения-сложения за проход

    В этой части мы возьмём первый из пропусков BLIS — микроядро sgemm ; сначала зафиксируем форму аккумулятора 32×32 в четырёх тайлах ZA, затем разберём горячий цикл по K, потом эпилог с alpha , beta и ловушкой NaN, а в конце посмотрим, какие числа производительности даёт именно это ядро. Следующая часть оставит структуру почти той же, но заменит геометрию тайла и условия существования ядра.

    habr.com/ru/articles/1071462/

    #BLIS #GEMM #SME2 #Apple_Silicon #микроядро #кэшблокинг #упаковка_данных #высокопроизводительные_вычисления #линейная_алгебра #BLAS

  2. Микроядро SME2 sgemm: 1024 умножения-сложения за проход

    В этой части мы возьмём первый из пропусков BLIS — микроядро sgemm ; сначала зафиксируем форму аккумулятора 32×32 в четырёх тайлах ZA, затем разберём горячий цикл по K, потом эпилог с alpha , beta и ловушкой NaN, а в конце посмотрим, какие числа производительности даёт именно это ядро. Следующая часть оставит структуру почти той же, но заменит геометрию тайла и условия существования ядра.

    habr.com/ru/articles/1071462/

    #BLIS #GEMM #SME2 #Apple_Silicon #микроядро #кэшблокинг #упаковка_данных #высокопроизводительные_вычисления #линейная_алгебра #BLAS

  3. Микроядро SME2 sgemm: 1024 умножения-сложения за проход

    В этой части мы возьмём первый из пропусков BLIS — микроядро sgemm ; сначала зафиксируем форму аккумулятора 32×32 в четырёх тайлах ZA, затем разберём горячий цикл по K, потом эпилог с alpha , beta и ловушкой NaN, а в конце посмотрим, какие числа производительности даёт именно это ядро. Следующая часть оставит структуру почти той же, но заменит геометрию тайла и условия существования ядра.

    habr.com/ru/articles/1071462/

    #BLIS #GEMM #SME2 #Apple_Silicon #микроядро #кэшблокинг #упаковка_данных #высокопроизводительные_вычисления #линейная_алгебра #BLAS

  4. BLIS: недостающую среднюю ступеньку построили тридцать лет назад

    В этой части мы начнём с тупика, в который приводит голый цикл FMOPA ; затем покажем, какую часть GEMM BLIS уже построил за нас; после этого разберём пять циклов BLIS и место микроядра внутри них. Финал главы должен сделать дальнейший план конкретным: что именно нужно добавить для Apple SME, а что уже относится к готовой «мебели» фреймворка.

    habr.com/ru/articles/1069058/

    #BLIS #GEMM #SME2 #Apple_Silicon #микроядро #кэшблокинг #упаковка_данных #высокопроизводительные_вычисления #линейная_алгебра #BLAS

  5. BLIS: недостающую среднюю ступеньку построили тридцать лет назад

    В этой части мы начнём с тупика, в который приводит голый цикл FMOPA ; затем покажем, какую часть GEMM BLIS уже построил за нас; после этого разберём пять циклов BLIS и место микроядра внутри них. Финал главы должен сделать дальнейший план конкретным: что именно нужно добавить для Apple SME, а что уже относится к готовой «мебели» фреймворка.

    habr.com/ru/articles/1069058/

    #BLIS #GEMM #SME2 #Apple_Silicon #микроядро #кэшблокинг #упаковка_данных #высокопроизводительные_вычисления #линейная_алгебра #BLAS

  6. BLIS: недостающую среднюю ступеньку построили тридцать лет назад

    В этой части мы начнём с тупика, в который приводит голый цикл FMOPA ; затем покажем, какую часть GEMM BLIS уже построил за нас; после этого разберём пять циклов BLIS и место микроядра внутри них. Финал главы должен сделать дальнейший план конкретным: что именно нужно добавить для Apple SME, а что уже относится к готовой «мебели» фреймворка.

    habr.com/ru/articles/1069058/

    #BLIS #GEMM #SME2 #Apple_Silicon #микроядро #кэшблокинг #упаковка_данных #высокопроизводительные_вычисления #линейная_алгебра #BLAS

  7. Re-reading the old BLAS level 3 and #FLAME papers about microkernels and performance for performant #GEMM implementations in #BLAS, #GotoBLAS and #BLIS. I had forgotten how well written they are!

  8. Re-reading the old BLAS level 3 and #FLAME papers about microkernels and performance for performant #GEMM implementations in #BLAS, #GotoBLAS and #BLIS. I had forgotten how well written they are!

  9. Question for the #stats folks working with #mgcv and #gam / #bam:
    I'm dealing with a dataset with a high temporal autocorrelation, so after a lengthy discussion with the author of `gratia` (my current PI), we concluded that I should move away from AR(1) models and rather work with #NCV.
    No problems with the setup, but the run time is forever.
    My first model has been running for 20h by now, with no indication of how long it will take.
    I have already switched over to #OpenBLAS, but it seems weird that my CPU load is constantly at only 15-25%. The only indication that something is happening is that RAM usage is slowly but steadily increasing.
    I'm dealing with ~40k data points across ~300 time series, and a NCV window of 7 data points, so nothing crazy. The model includes two- and three-way interactions, and random smooths, but all of those things are biologically relevant.

    I'd happily take any suggestions on how to speed things up, how to get proper CPU usage, or at least get an estimate of how far along the calculations are.

    I might eventually need to switch over to #twlss, from the current `tw()`, and that will make things worse as that is not supported by `bam()`.

    I'm currently on Windows, but I might be able to run things on an #HPC if needed, but not sure if I can easily fiddle with #BLAS there.

  10. Question for the #stats folks working with #mgcv and #gam / #bam:
    I'm dealing with a dataset with a high temporal autocorrelation, so after a lengthy discussion with the author of `gratia` (my current PI), we concluded that I should move away from AR(1) models and rather work with #NCV.
    No problems with the setup, but the run time is forever.
    My first model has been running for 20h by now, with no indication of how long it will take.
    I have already switched over to #OpenBLAS, but it seems weird that my CPU load is constantly at only 15-25%. The only indication that something is happening is that RAM usage is slowly but steadily increasing.
    I'm dealing with ~40k data points across ~300 time series, and a NCV window of 7 data points, so nothing crazy. The model includes two- and three-way interactions, and random smooths, but all of those things are biologically relevant.

    I'd happily take any suggestions on how to speed things up, how to get proper CPU usage, or at least get an estimate of how far along the calculations are.

    I might eventually need to switch over to #twlss, from the current `tw()`, and that will make things worse as that is not supported by `bam()`.

    I'm currently on Windows, but I might be able to run things on an #HPC if needed, but not sure if I can easily fiddle with #BLAS there.

  11. Question for the #stats folks working with #mgcv and #gam / #bam:
    I'm dealing with a dataset with a high temporal autocorrelation, so after a lengthy discussion with the author of `gratia` (my current PI), we concluded that I should move away from AR(1) models and rather work with #NCV.
    No problems with the setup, but the run time is forever.
    My first model has been running for 20h by now, with no indication of how long it will take.
    I have already switched over to #OpenBLAS, but it seems weird that my CPU load is constantly at only 15-25%. The only indication that something is happening is that RAM usage is slowly but steadily increasing.
    I'm dealing with ~40k data points across ~300 time series, and a NCV window of 7 data points, so nothing crazy. The model includes two- and three-way interactions, and random smooths, but all of those things are biologically relevant.

    I'd happily take any suggestions on how to speed things up, how to get proper CPU usage, or at least get an estimate of how far along the calculations are.

    I might eventually need to switch over to #twlss, from the current `tw()`, and that will make things worse as that is not supported by `bam()`.

    I'm currently on Windows, but I might be able to run things on an #HPC if needed, but not sure if I can easily fiddle with #BLAS there.

  12. Question for the #stats folks working with #mgcv and #gam / #bam:
    I'm dealing with a dataset with a high temporal autocorrelation, so after a lengthy discussion with the author of `gratia` (my current PI), we concluded that I should move away from AR(1) models and rather work with #NCV.
    No problems with the setup, but the run time is forever.
    My first model has been running for 20h by now, with no indication of how long it will take.
    I have already switched over to #OpenBLAS, but it seems weird that my CPU load is constantly at only 15-25%. The only indication that something is happening is that RAM usage is slowly but steadily increasing.
    I'm dealing with ~40k data points across ~300 time series, and a NCV window of 7 data points, so nothing crazy. The model includes two- and three-way interactions, and random smooths, but all of those things are biologically relevant.

    I'd happily take any suggestions on how to speed things up, how to get proper CPU usage, or at least get an estimate of how far along the calculations are.

    I might eventually need to switch over to #twlss, from the current `tw()`, and that will make things worse as that is not supported by `bam()`.

    I'm currently on Windows, but I might be able to run things on an #HPC if needed, but not sure if I can easily fiddle with #BLAS there.

  13. Did you recently update your #rstats to 4.6? Is your matrix algebra slow? Not #BLAS ting? `sessionInfo()` shows which BLAS library R uses. Switching from reference BLAS to Apple Accelerate is easily a 50x speedup.

    Let me know if this worked for you. 🚀

    Post: uatz.org/blog/2026-06-04-r-blas-macos/ #rstats

  14. Did you recently update your #rstats to 4.6? Is your matrix algebra slow? Not #BLAS ting? `sessionInfo()` shows which BLAS library R uses. Switching from reference BLAS to Apple Accelerate is easily a 50x speedup.

    Let me know if this worked for you. 🚀

    Post: uatz.org/blog/2026-06-04-r-blas-macos/ #rstats

  15. Did you recently update your #rstats to 4.6? Is your matrix algebra slow? Not #BLAS ting? `sessionInfo()` shows which BLAS library R uses. Switching from reference BLAS to Apple Accelerate is easily a 50x speedup.

    Let me know if this worked for you. 🚀

    Post: uatz.org/blog/2026-06-04-r-blas-macos/ #rstats

  16. Did you recently update your #rstats to 4.6? Is your matrix algebra slow? Not #BLAS ting? `sessionInfo()` shows which BLAS library R uses. Switching from reference BLAS to Apple Accelerate is easily a 50x speedup.

    Let me know if this worked for you. 🚀

    Post: uatz.org/blog/2026-06-04-r-blas-macos/ #rstats

  17. Did you recently update your #rstats to 4.6? Is your matrix algebra slow? Not #BLAS ting? `sessionInfo()` shows which BLAS library R uses. Switching from reference BLAS to Apple Accelerate is easily a 50x speedup.

    Let me know if this worked for you. 🚀

    Post: uatz.org/blog/2026-06-04-r-blas-macos/ #rstats

  18. #Copilot and I are about 30% away from creating a #Pascal version of #LAPACK using #BLAS. We are about two days away from achieving 80% of LAPACK. Then we will tweak it using some GPU acceleration to make its speed comparable to some python libraries like Numpy.

    It is important to note that one must be very disciplined in keeping clean documentations, a thorough and tight testing cycle, a rigid workflow pattern, or an AI will tend to skip tests, become sloppy and lose focus.

    #AI #LLM

  19. #Copilot and I are about 30% away from creating a #Pascal version of #LAPACK using #BLAS. We are about two days away from achieving 80% of LAPACK. Then we will tweak it using some GPU acceleration to make its speed comparable to some python libraries like Numpy.

    It is important to note that one must be very disciplined in keeping clean documentations, a thorough and tight testing cycle, a rigid workflow pattern, or an AI will tend to skip tests, become sloppy and lose focus.

    #AI #LLM

  20. #Copilot and I are about 30% away from creating a #Pascal version of #LAPACK using #BLAS. We are about two days away from achieving 80% of LAPACK. Then we will tweak it using some GPU acceleration to make its speed comparable to some python libraries like Numpy.

    It is important to note that one must be very disciplined in keeping clean documentations, a thorough and tight testing cycle, a rigid workflow pattern, or an AI will tend to skip tests, become sloppy and lose focus.

    #AI #LLM

  21. #Copilot and I are about 30% away from creating a #Pascal version of #LAPACK using #BLAS. We are about two days away from achieving 80% of LAPACK. Then we will tweak it using some GPU acceleration to make its speed comparable to some python libraries like Numpy.

    It is important to note that one must be very disciplined in keeping clean documentations, a thorough and tight testing cycle, a rigid workflow pattern, or an AI will tend to skip tests, become sloppy and lose focus.

    #AI #LLM

  22. #AI illiteracy is real. While still arguing with a bunch of AI haters, #Copilot and I just finished our #Pascal #BLAS level 1-3 Implementation plus eigenvalue, cholesky, and sparse #matrix, so we will never need #python, #C, C#, #Rust, ... for our Small Language Project. We will expand our Pascal Numeric Library (PNL) v1.0 to something like #Numpy and #Pytorch, but with static arrays, deterministic data structure, no referencing, no pointer arithmetic.

    #LLM #programming #computer

  23. #AI illiteracy is real. While still arguing with a bunch of AI haters, #Copilot and I just finished our #Pascal #BLAS level 1-3 Implementation plus eigenvalue, cholesky, and sparse #matrix, so we will never need #python, #C, C#, #Rust, ... for our Small Language Project. We will expand our Pascal Numeric Library (PNL) v1.0 to something like #Numpy and #Pytorch, but with static arrays, deterministic data structure, no referencing, no pointer arithmetic.

    #LLM #programming #computer

  24. #AI illiteracy is real. While still arguing with a bunch of AI haters, #Copilot and I just finished our #Pascal #BLAS level 1-3 Implementation plus eigenvalue, cholesky, and sparse #matrix, so we will never need #python, #C, C#, #Rust, ... for our Small Language Project. We will expand our Pascal Numeric Library (PNL) v1.0 to something like #Numpy and #Pytorch, but with static arrays, deterministic data structure, no referencing, no pointer arithmetic.

    #LLM #programming #computer

  25. #AI illiteracy is real. While still arguing with a bunch of AI haters, #Copilot and I just finished our #Pascal #BLAS level 1-3 Implementation plus eigenvalue, cholesky, and sparse #matrix, so we will never need #python, #C, C#, #Rust, ... for our Small Language Project. We will expand our Pascal Numeric Library (PNL) v1.0 to something like #Numpy and #Pytorch, but with static arrays, deterministic data structure, no referencing, no pointer arithmetic.

    #LLM #programming #computer

  26. While arguing with some AI haters, #Copilot and I created this Pure #Pascal #BLAS (Level 1,2,3 Core) Implementation in less than 1 day. We encountered many serious problems, including drifting of workflow pattern, getting stuck in a Delphi error loop, overhauling our original design... But as long as you understand AI, keep good documentations, maintain the core structure of the problem,.. you will be able to work with AI successfully. Don't hesitate to use more than one #AI at a time.

    #LLM

  27. While arguing with some AI haters, #Copilot and I created this Pure #Pascal #BLAS (Level 1,2,3 Core) Implementation in less than 1 day. We encountered many serious problems, including drifting of workflow pattern, getting stuck in a Delphi error loop, overhauling our original design... But as long as you understand AI, keep good documentations, maintain the core structure of the problem,.. you will be able to work with AI successfully. Don't hesitate to use more than one #AI at a time.

    #LLM

  28. While arguing with some AI haters, #Copilot and I created this Pure #Pascal #BLAS (Level 1,2,3 Core) Implementation in less than 1 day. We encountered many serious problems, including drifting of workflow pattern, getting stuck in a Delphi error loop, overhauling our original design... But as long as you understand AI, keep good documentations, maintain the core structure of the problem,.. you will be able to work with AI successfully. Don't hesitate to use more than one #AI at a time.

    #LLM

  29. While arguing with some AI haters, #Copilot and I created this Pure #Pascal #BLAS (Level 1,2,3 Core) Implementation in less than 1 day. We encountered many serious problems, including drifting of workflow pattern, getting stuck in a Delphi error loop, overhauling our original design... But as long as you understand AI, keep good documentations, maintain the core structure of the problem,.. you will be able to work with AI successfully. Don't hesitate to use more than one #AI at a time.

    #LLM

  30. What is #BLAS?

    BLAS is a set of fast matrix routines originally written in #Fortran.
    If you’re tired of dynamic types, hidden references, ownership rules, and endless “stream” abstractions, Free #Pascal + BLAS gives you old‑school, deterministic HPC #programming with none of the modern noise.

    #Copilot and I will be using Free Pascal and BLAS for our Small Language Model project #SLM. No more #C, #python, #Rust, or C#

    #AI #LLM #computer

  31. What is #BLAS?

    BLAS is a set of fast matrix routines originally written in #Fortran.
    If you’re tired of dynamic types, hidden references, ownership rules, and endless “stream” abstractions, Free #Pascal + BLAS gives you old‑school, deterministic HPC #programming with none of the modern noise.

    #Copilot and I will be using Free Pascal and BLAS for our Small Language Model project #SLM. No more #C, #python, #Rust, or C#

    #AI #LLM #computer

  32. What is #BLAS?

    BLAS is a set of fast matrix routines originally written in #Fortran.
    If you’re tired of dynamic types, hidden references, ownership rules, and endless “stream” abstractions, Free #Pascal + BLAS gives you old‑school, deterministic HPC #programming with none of the modern noise.

    #Copilot and I will be using Free Pascal and BLAS for our Small Language Model project #SLM. No more #C, #python, #Rust, or C#

    #AI #LLM #computer

  33. What is #BLAS?

    BLAS is a set of fast matrix routines originally written in #Fortran.
    If you’re tired of dynamic types, hidden references, ownership rules, and endless “stream” abstractions, Free #Pascal + BLAS gives you old‑school, deterministic HPC #programming with none of the modern noise.

    #Copilot and I will be using Free Pascal and BLAS for our Small Language Model project #SLM. No more #C, #python, #Rust, or C#

    #AI #LLM #computer

  34. Why do people use #python, a glue language, which is so slow? The only reason is the AI ecosystem.

    #Copilot and I just tested Free Pascal and BLAS for its speed without using #numpy or #pytorch. The result is amazing. It took less than a second to do a 1024x1024 #matrix multiplication.

    We will be using Free #Pascal and #BLAS to write our Small Language Model #SLM using #NNUE.

    #AI #LLM

  35. Why do people use #python, a glue language, which is so slow? The only reason is the AI ecosystem.

    #Copilot and I just tested Free Pascal and BLAS for its speed without using #numpy or #pytorch. The result is amazing. It took less than a second to do a 1024x1024 #matrix multiplication.

    We will be using Free #Pascal and #BLAS to write our Small Language Model #SLM using #NNUE.

    #AI #LLM

  36. Why do people use #python, a glue language, which is so slow? The only reason is the AI ecosystem.

    #Copilot and I just tested Free Pascal and BLAS for its speed without using #numpy or #pytorch. The result is amazing. It took less than a second to do a 1024x1024 #matrix multiplication.

    We will be using Free #Pascal and #BLAS to write our Small Language Model #SLM using #NNUE.

    #AI #LLM

  37. Why do people use #python, a glue language, which is so slow? The only reason is the AI ecosystem.

    #Copilot and I just tested Free Pascal and BLAS for its speed without using #numpy or #pytorch. The result is amazing. It took less than a second to do a 1024x1024 #matrix multiplication.

    We will be using Free #Pascal and #BLAS to write our Small Language Model #SLM using #NNUE.

    #AI #LLM

  38. 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

  39. 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

  40. 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

  41. 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

  42. 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

  43. 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

  44. 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

  45. 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

  46. 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

  47. 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

  48. 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

  49. 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

  50. 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

  51. 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