home.social

#parallelcomputing — Public Fediverse posts

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

  1. We had a very productive F2F meeting last week at the Argonne Leadership Computing Facility, with many thanks to our great hosts at the Argonne National Lab. The main objective was to feature-freeze OpenMP API version 6.1 and we accomplished that mission!

    #OpenMP #ParallelComputing #HPC

  2. We had a very productive F2F meeting last week at the Argonne Leadership Computing Facility, with many thanks to our great hosts at the Argonne National Lab. The main objective was to feature-freeze OpenMP API version 6.1 and we accomplished that mission!

    #OpenMP #ParallelComputing #HPC

  3. We had a very productive F2F meeting last week at the Argonne Leadership Computing Facility, with many thanks to our great hosts at the Argonne National Lab. The main objective was to feature-freeze OpenMP API version 6.1 and we accomplished that mission!

    #OpenMP #ParallelComputing #HPC

  4. We had a very productive F2F meeting last week at the Argonne Leadership Computing Facility, with many thanks to our great hosts at the Argonne National Lab. The main objective was to feature-freeze OpenMP API version 6.1 and we accomplished that mission!

    #OpenMP #ParallelComputing #HPC

  5. Sharing big R objects across processes shouldn’t mean copying them over and over.

    mori uses shared memory + ALTREP to give you zero-copy access—multiple processes, one underlying object.

    Fast, memory-efficient, and built for modern parallel workflows.

    👉 shikokuchuo.net/mori/

    #rstats #datascience #parallelcomputing

  6. The OpenMP Architecture Review Board has formed a #Python Language Subcommittee — a significant step toward bringing standardized shared-memory parallelism to the world's most widely used programming language.

    The subcommittee's goal is to define #OpenMP directive support for Python and include it in the OpenMP API 7.0 specification, targeted for 2029.

    openmp.org/2026/python-subcomi
    #HPC #parallelcomputing

  7. The OpenMP Architecture Review Board has formed a #Python Language Subcommittee — a significant step toward bringing standardized shared-memory parallelism to the world's most widely used programming language.

    The subcommittee's goal is to define #OpenMP directive support for Python and include it in the OpenMP API 7.0 specification, targeted for 2029.

    openmp.org/2026/python-subcomi
    #HPC #parallelcomputing

  8. The OpenMP Architecture Review Board has formed a #Python Language Subcommittee — a significant step toward bringing standardized shared-memory parallelism to the world's most widely used programming language.

    The subcommittee's goal is to define #OpenMP directive support for Python and include it in the OpenMP API 7.0 specification, targeted for 2029.

    openmp.org/2026/python-subcomi
    #HPC #parallelcomputing

  9. The OpenMP Architecture Review Board has formed a #Python Language Subcommittee — a significant step toward bringing standardized shared-memory parallelism to the world's most widely used programming language.

    The subcommittee's goal is to define #OpenMP directive support for Python and include it in the OpenMP API 7.0 specification, targeted for 2029.

    openmp.org/2026/python-subcomi
    #HPC #parallelcomputing

  10. The OpenMP Architecture Review Board has formed a #Python Language Subcommittee — a significant step toward bringing standardized shared-memory parallelism to the world's most widely used programming language.

    The subcommittee's goal is to define #OpenMP directive support for Python and include it in the OpenMP API 7.0 specification, targeted for 2029.

    openmp.org/2026/python-subcomi
    #HPC #parallelcomputing

  11. 🎉 Wow, #groundbreaking revelation: when you give a hungry #AI agent a buffet of GPUs, it eats faster! 🚀 Who knew? Apparently, parallel computing is a thing now. 🙄 Thanks for the 12-minute read on how technology works, we were all clueless. 😂
    blog.skypilot.co/scaling-autor #parallelcomputing #technews #GPUbuffet #humor #HackerNews #ngated

  12. Questa settimana ho fatto la-due-giorni-a-Bologna 🚀🚀

    Intensa di #talk ispiranti, #gadget bellissimi … e le persone hanno reso tutto davvero indimenticabile. ✨

    Conosco i retroscena dell’organizzazione e i ragazzi del @grusp hanno resto tutto perfetto, leggero e spensierato .. sebbene non fosse per nulla facile 💪

    E’ sempre un piacere essere accettati come #speaker ai loro eventi ❤️

    Alla prossima !

    #DataAnalysis #Dask #Kubernetes #ParallelComputing #Scalability #AWS #DevSecOpsDay #ContainerDay

  13. Questa settimana ho fatto la due giorni a Bologna di #DevSecOpsDay e #ContainerDay 🚀

    Intensa di #talk ispiranti, #gadget bellissimi … e le persone hanno reso tutto davvero indimenticabile. ✨

    Conosco i retroscena dell’organizzazione e i ragazzi del @grusp hanno resto tutto perfetto, leggero e spensierato .. sebbene non fosse per nulla facile 💪

    E’ sempre un piacere essere accettati come #speaker ai loro eventi ❤️

    Alla prossima !

    #DataAnalysis #Dask #Kubernetes #ParallelComputing #Scalability

  14. Questa settimana ho fatto la due giorni a Bologna di #DevSecOpsDay e #ContainerDay 🚀

    Intensa di #talk ispiranti, #gadget bellissimi … e le persone hanno reso tutto davvero indimenticabile. ✨

    Conosco i retroscena dell’organizzazione e i ragazzi del @grusp hanno resto tutto perfetto, leggero e spensierato .. sebbene non fosse per nulla facile 💪

    E’ sempre un piacere essere accettati come #speaker ai loro eventi ❤️

    Alla prossima !

    #DataAnalysis #Dask #Kubernetes #ParallelComputing #Scalability

  15. Questa settimana ho fatto la due giorni a Bologna di #DevSecOpsDay e #ContainerDay 🚀

    Intensa di #talk ispiranti, #gadget bellissimi … e le persone hanno reso tutto davvero indimenticabile. ✨

    Conosco i retroscena dell’organizzazione e i ragazzi del @grusp hanno resto tutto perfetto, leggero e spensierato .. sebbene non fosse per nulla facile 💪

    E’ sempre un piacere essere accettati come #speaker ai loro eventi ❤️

    Alla prossima !

    #DataAnalysis #Dask #Kubernetes #ParallelComputing #Scalability

  16. Questa settimana ho fatto la-due-giorni-a-Bologna 🚀🚀

    Intensa di #talk ispiranti, #gadget bellissimi … e le persone hanno reso tutto davvero indimenticabile. ✨

    Conosco i retroscena dell’organizzazione e i ragazzi del @grusp hanno resto tutto perfetto, leggero e spensierato .. sebbene non fosse per nulla facile 💪

    E’ sempre un piacere essere accettati come #speaker ai loro eventi ❤️

    Alla prossima !

    #DataAnalysis #Dask #Kubernetes #ParallelComputing #Scalability #AWS #DevSecOpsDay #ContainerDay

  17. Efficient GPU algorithm converts Bézier paths into renderable geometry, enabling real-time, cross-platform vector graphics rendering. hackernoon.com/implementing-da #parallelcomputing

  18. Efficiently convert cubic Bézier curves to Euler spirals for smoother GPU rendering and accurate parallel curve computations. hackernoon.com/how-to-convert- #parallelcomputing

  19. Today I introduced a much-needed feature to #GPUSPH.

    Our code supports multi-GPU and even multi-node, so in general if you have a large simulation you'll want to distribute it over all your GPUs using our internal support for it.

    However, in some cases, you need to run a battery of simulations and your problem size isn't large enough to justify the use of more than a couple of GPUs for each simulation.

    In this case, rather than running the simulations in your set serially (one after the other) using all GPUs for each, you'll want to run them in parallel, potentially even each on a single GPUs.

    The idea is to find the next avaialble (set of) GPU(s) and launch a simulation on them while there are still available sets, then wait until a “slot” frees up and start the new one(s) as slots get freed.

    Until now, we've been doing this manually by partitioning the set of simulations to do and start them in different shells.

    There is actually a very powerful tool to achieve this on the command, line, GNU Parallel. As with all powerful tools, however, this is somewhat cumbersome to configure to get the intended result. And after Doing It Right™ one must remember the invocation magic …

    So today I found some time to write a wrapper around GNU Parallel that basically (1) enumerates the available GPUs and (2) appends the appropriate --device command-line option to the invocation of GPUSPH, based on the slot number.

    #GPGPU #ParallelComputing #DistributedComputing #GNUParallel

  20. Today I introduced a much-needed feature to #GPUSPH.

    Our code supports multi-GPU and even multi-node, so in general if you have a large simulation you'll want to distribute it over all your GPUs using our internal support for it.

    However, in some cases, you need to run a battery of simulations and your problem size isn't large enough to justify the use of more than a couple of GPUs for each simulation.

    In this case, rather than running the simulations in your set serially (one after the other) using all GPUs for each, you'll want to run them in parallel, potentially even each on a single GPUs.

    The idea is to find the next avaialble (set of) GPU(s) and launch a simulation on them while there are still available sets, then wait until a “slot” frees up and start the new one(s) as slots get freed.

    Until now, we've been doing this manually by partitioning the set of simulations to do and start them in different shells.

    There is actually a very powerful tool to achieve this on the command, line, GNU Parallel. As with all powerful tools, however, this is somewhat cumbersome to configure to get the intended result. And after Doing It Right™ one must remember the invocation magic …

    So today I found some time to write a wrapper around GNU Parallel that basically (1) enumerates the available GPUs and (2) appends the appropriate --device command-line option to the invocation of GPUSPH, based on the slot number.

    #GPGPU #ParallelComputing #DistributedComputing #GNUParallel

  21. Today I introduced a much-needed feature to #GPUSPH.

    Our code supports multi-GPU and even multi-node, so in general if you have a large simulation you'll want to distribute it over all your GPUs using our internal support for it.

    However, in some cases, you need to run a battery of simulations and your problem size isn't large enough to justify the use of more than a couple of GPUs for each simulation.

    In this case, rather than running the simulations in your set serially (one after the other) using all GPUs for each, you'll want to run them in parallel, potentially even each on a single GPUs.

    The idea is to find the next avaialble (set of) GPU(s) and launch a simulation on them while there are still available sets, then wait until a “slot” frees up and start the new one(s) as slots get freed.

    Until now, we've been doing this manually by partitioning the set of simulations to do and start them in different shells.

    There is actually a very powerful tool to achieve this on the command, line, GNU Parallel. As with all powerful tools, however, this is somewhat cumbersome to configure to get the intended result. And after Doing It Right™ one must remember the invocation magic …

    So today I found some time to write a wrapper around GNU Parallel that basically (1) enumerates the available GPUs and (2) appends the appropriate --device command-line option to the invocation of GPUSPH, based on the slot number.

    #GPGPU #ParallelComputing #DistributedComputing #GNUParallel

  22. Today I introduced a much-needed feature to #GPUSPH.

    Our code supports multi-GPU and even multi-node, so in general if you have a large simulation you'll want to distribute it over all your GPUs using our internal support for it.

    However, in some cases, you need to run a battery of simulations and your problem size isn't large enough to justify the use of more than a couple of GPUs for each simulation.

    In this case, rather than running the simulations in your set serially (one after the other) using all GPUs for each, you'll want to run them in parallel, potentially even each on a single GPUs.

    The idea is to find the next avaialble (set of) GPU(s) and launch a simulation on them while there are still available sets, then wait until a “slot” frees up and start the new one(s) as slots get freed.

    Until now, we've been doing this manually by partitioning the set of simulations to do and start them in different shells.

    There is actually a very powerful tool to achieve this on the command, line, GNU Parallel. As with all powerful tools, however, this is somewhat cumbersome to configure to get the intended result. And after Doing It Right™ one must remember the invocation magic …

    So today I found some time to write a wrapper around GNU Parallel that basically (1) enumerates the available GPUs and (2) appends the appropriate --device command-line option to the invocation of GPUSPH, based on the slot number.

    #GPGPU #ParallelComputing #DistributedComputing #GNUParallel

  23. Today I introduced a much-needed feature to #GPUSPH.

    Our code supports multi-GPU and even multi-node, so in general if you have a large simulation you'll want to distribute it over all your GPUs using our internal support for it.

    However, in some cases, you need to run a battery of simulations and your problem size isn't large enough to justify the use of more than a couple of GPUs for each simulation.

    In this case, rather than running the simulations in your set serially (one after the other) using all GPUs for each, you'll want to run them in parallel, potentially even each on a single GPUs.

    The idea is to find the next avaialble (set of) GPU(s) and launch a simulation on them while there are still available sets, then wait until a “slot” frees up and start the new one(s) as slots get freed.

    Until now, we've been doing this manually by partitioning the set of simulations to do and start them in different shells.

    There is actually a very powerful tool to achieve this on the command, line, GNU Parallel. As with all powerful tools, however, this is somewhat cumbersome to configure to get the intended result. And after Doing It Right™ one must remember the invocation magic …

    So today I found some time to write a wrapper around GNU Parallel that basically (1) enumerates the available GPUs and (2) appends the appropriate --device command-line option to the invocation of GPUSPH, based on the slot number.

    #GPGPU #ParallelComputing #DistributedComputing #GNUParallel

  24. We are excited to return to Supercomputing! Join us on Sunday, November 16th for the OpenMP tutorial, Mastering OpenMP Tasking. This tutorial will provide performance and scalability recipes to improve the performance of OpenMP tasking applications.

    Learn more about all of OpenMP's activities at #SC25 at: openmp.org/events/sc25/
    #OpenMP #Tasking #parallelcomputing #hpc #multiprocessor

  25. Join us at Supercomputing 2025 in St. Louis!

    We have a packed agenda at this year's show with BOFs and tutorials, and be sure to join us in booth #911 to meet with OpenMP experts to ask your toughest questions, enter the daily Book Drawing, get your free OpenMP API 6.0 reference guide, and have an afternoon beverage.

    Learn more: openmp.org/events/sc25/
    #SC25 #OpenMP #parallelcomputing #hpc #gpu #pyomp

  26. Join us at Supercomputing 2025 in St. Louis!

    We have a packed agenda at this year's show with BOFs and tutorials, and be sure to join us in booth #911 to meet with OpenMP experts to ask your toughest questions, enter the daily Book Drawing, get your free OpenMP API 6.0 reference guide, and have an afternoon beverage.

    Learn more: openmp.org/events/sc25/
    #SC25 #OpenMP #parallelcomputing #hpc #gpu #pyomp

  27. Wir freuen uns, Euch auch in diesem Jahr wieder spannende MATLAB-Kurse im Online-Format in der GWDG Academy anzubieten, welche von MathWorks-Mitarbeitern durchgeführt werden:

    💠 Parallel Computing with MATLAB
    Termin: 17.11.2025, 10:00 – 13:00 Uhr
    💠 Demo Session: Scaling up MATLAB to the GWDG Scientific Compute Cluster
    Termin: 19.11.2025, 15:00 – 16:30 Uhr
    💠 Introduction to Research Software Development with MATLAB
    Termin: 20.11.2025, 09:00 – 12:00 Uhr
    💠 Connecting MATLAB with Python and other Open Source Tools
    Termin: 20.11.2025 14:00 – 17:00 Uhr

    Die Kurstermine werden ergänzt um eine sogenannte Office Hour (online) am 21.11.2025, 14:00 – 15:00 Uhr, während der Fragen zu den vorgestellten Themen der Kurse ausgiebig gestellt und behandelt werden können, um einen Austausch zwischen den Teilnehmer*innen und den Dozenten zu erreichen.

    🔗 s.gwdg.de/NRjJYK

    #gwdg #academy #gwdgacademy #kurs #matlab #parallelcomputing #göttingen #unigöttingen #mathswork

  28. 📢 OpenMP Newsletter – July 2025 Edition

    Highlights:

    🗓️ IWOMP 2025 preliminary program
    👥 3 new members join the OpenMP Architecture Review Board
    🛠️ OpenMP support in:

    * GCC 15.1

    * Intel oneAPI HPC Toolkit 2025.2

    * NumPy 2.3

    Full newsletter: mailchi.mp/e82391a1d7b0/thanks

    🔗 openmp.org

    #OpenMP #HPC #IWOMP2025 #ParallelComputing #NumPy #GCC #InteloneAPI

  29. 📢 OpenMP Newsletter – July 2025 Edition

    Highlights:

    🗓️ IWOMP 2025 preliminary program
    👥 3 new members join the OpenMP Architecture Review Board
    🛠️ OpenMP support in:

    * GCC 15.1

    * Intel oneAPI HPC Toolkit 2025.2

    * NumPy 2.3

    Full newsletter: mailchi.mp/e82391a1d7b0/thanks

    🔗 openmp.org

    #OpenMP #HPC #IWOMP2025 #ParallelComputing #NumPy #GCC #InteloneAPI

  30. 📢 OpenMP Newsletter – July 2025 Edition

    Highlights:

    🗓️ IWOMP 2025 preliminary program
    👥 3 new members join the OpenMP Architecture Review Board
    🛠️ OpenMP support in:

    * GCC 15.1

    * Intel oneAPI HPC Toolkit 2025.2

    * NumPy 2.3

    Full newsletter: mailchi.mp/e82391a1d7b0/thanks

    🔗 openmp.org

    #OpenMP #HPC #IWOMP2025 #ParallelComputing #NumPy #GCC #InteloneAPI

  31. 📢 OpenMP Newsletter – July 2025 Edition

    Highlights:

    🗓️ IWOMP 2025 preliminary program
    👥 3 new members join the OpenMP Architecture Review Board
    🛠️ OpenMP support in:

    * GCC 15.1

    * Intel oneAPI HPC Toolkit 2025.2

    * NumPy 2.3

    Full newsletter: mailchi.mp/e82391a1d7b0/thanks

    🔗 openmp.org

    #OpenMP #HPC #IWOMP2025 #ParallelComputing #NumPy #GCC #InteloneAPI

  32. 📢 OpenMP Newsletter – July 2025 Edition

    Highlights:

    🗓️ IWOMP 2025 preliminary program
    👥 3 new members join the OpenMP Architecture Review Board
    🛠️ OpenMP support in:

    * GCC 15.1

    * Intel oneAPI HPC Toolkit 2025.2

    * NumPy 2.3

    Full newsletter: mailchi.mp/e82391a1d7b0/thanks

    🔗 openmp.org

    #OpenMP #HPC #IWOMP2025 #ParallelComputing #NumPy #GCC #InteloneAPI

  33. Going to the (Parallel) Chapel - There is always the promise of using more computing power for a single task. Your ... - hackaday.com/2025/07/06/going- #softwaredevelopment #parallelcomputing

  34. 📸 Full house at the OpenMP BOF at #ISC25 — over 140 attendees joined us in Hamburg! 🎉

    Our session "What to Expect from OpenMP API Version 6.0" covered:

    ✅ A dive into key features of OpenMP 6.0
    ✅ A preview of 6.1 and 7.0
    ✅ Updates from toolchain developers
    ✅ Lively Q&A to help shape future OpenMP directions

    Thanks to everyone who contributed — your feedback is powering the future of parallel programming! 💡

    #OpenMP #HPC #ISC2025 #OpenMP6 #ParallelComputing #Supercomputing

  35. 📸 Full house at the OpenMP BOF at #ISC25 — over 140 attendees joined us in Hamburg! 🎉

    Our session "What to Expect from OpenMP API Version 6.0" covered:

    ✅ A dive into key features of OpenMP 6.0
    ✅ A preview of 6.1 and 7.0
    ✅ Updates from toolchain developers
    ✅ Lively Q&A to help shape future OpenMP directions

    Thanks to everyone who contributed — your feedback is powering the future of parallel programming! 💡

    #OpenMP #HPC #ISC2025 #OpenMP6 #ParallelComputing #Supercomputing

  36. 📸 Full house at the OpenMP BOF at #ISC25 — over 140 attendees joined us in Hamburg! 🎉

    Our session "What to Expect from OpenMP API Version 6.0" covered:

    ✅ A dive into key features of OpenMP 6.0
    ✅ A preview of 6.1 and 7.0
    ✅ Updates from toolchain developers
    ✅ Lively Q&A to help shape future OpenMP directions

    Thanks to everyone who contributed — your feedback is powering the future of parallel programming! 💡

    #OpenMP #HPC #ISC2025 #OpenMP6 #ParallelComputing #Supercomputing

  37. 📸 Full house at the OpenMP BOF at #ISC25 — over 140 attendees joined us in Hamburg! 🎉

    Our session "What to Expect from OpenMP API Version 6.0" covered:

    ✅ A dive into key features of OpenMP 6.0
    ✅ A preview of 6.1 and 7.0
    ✅ Updates from toolchain developers
    ✅ Lively Q&A to help shape future OpenMP directions

    Thanks to everyone who contributed — your feedback is powering the future of parallel programming! 💡

    #OpenMP #HPC #ISC2025 #OpenMP6 #ParallelComputing #Supercomputing

  38. 📸 Full house at the OpenMP BOF at #ISC25 — over 140 attendees joined us in Hamburg! 🎉

    Our session "What to Expect from OpenMP API Version 6.0" covered:

    ✅ A dive into key features of OpenMP 6.0
    ✅ A preview of 6.1 and 7.0
    ✅ Updates from toolchain developers
    ✅ Lively Q&A to help shape future OpenMP directions

    Thanks to everyone who contributed — your feedback is powering the future of parallel programming! 💡

    #OpenMP #HPC #ISC2025 #OpenMP6 #ParallelComputing #Supercomputing

  39. We’re excited to welcome NextSilicon to the OpenMP Architecture Review Board! 🎉

    Their Intelligent Compute Architecture blends adaptive computing with self-optimizing hardware/software and open frameworks like OpenMP. Together, we’re shaping a future of performant, portable, shared-memory parallelism. 💻🌐

    Read the press release:
    tinyurl.com/yksfbrah

    #OpenMP #NextSilicon #HPC #OpenStandards #ParallelComputing