#gvl — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gvl, aggregated by home.social.
-
„Wenn eine Verwertungsgesellschaft siegen kann, können es andere Institutionen auch. Go for it, #VGWort, VFF, #VGBildKunst, #GVL und Co!“
Ja! Das fände ich richtig und auch fair.
Leider braucht man bei Blogs da eine Mindestabrufzahl, auf die ich nicht komme.
-
„Wenn eine Verwertungsgesellschaft siegen kann, können es andere Institutionen auch. Go for it, #VGWort, VFF, #VGBildKunst, #GVL und Co!“
Ja! Das fände ich richtig und auch fair.
Leider braucht man bei Blogs da eine Mindestabrufzahl, auf die ich nicht komme.
-
SDB Scans the Ruby Stack Without the GVL
https://github.com/yfractal/blog/blob/master/blog/2025-01-15-non-blocking-stack-profiler.md
-
SDB Scans the Ruby Stack Without the GVL
https://github.com/yfractal/blog/blob/master/blog/2025-01-15-non-blocking-stack-profiler.md
-
So You Want To Remove The GVL?, by @byroot
https://byroot.github.io/ruby/performance/2025/01/29/so-you-want-to-remove-the-gvl.html> For quite a long time, it has been said that Rails applications are mostly IO-bound, hence #Ruby’s #GVL isn’t that big of a deal and that has influenced the design of some cornerstone pieces of Ruby infrastructure like #Puma and #Sidekiq. Regardless, the existence of the GVL still requires these threaded systems to use fork(2) in order to exploit all the cores of a server: one process per core.
-
So You Want To Remove The GVL?, by @byroot
https://byroot.github.io/ruby/performance/2025/01/29/so-you-want-to-remove-the-gvl.html> For quite a long time, it has been said that Rails applications are mostly IO-bound, hence #Ruby’s #GVL isn’t that big of a deal and that has influenced the design of some cornerstone pieces of Ruby infrastructure like #Puma and #Sidekiq. Regardless, the existence of the GVL still requires these threaded systems to use fork(2) in order to exploit all the cores of a server: one process per core.
