Discussion
Loading...

#Tag

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Tiago Mendes-Costa :ruby: and 1 other boosted
Giménez Silva Germán Alberto
Giménez Silva Germán Alberto
@gsgermanok@ruby.social  ·  activity timestamp 14 hours ago

When introducing parallelism in Rails,
the real danger isn’t threads.

It’s connection pool exhaustion.

Based on a Kaigi on Rails 2025 talk by @katakyo, I wrote a breakdown of how to safely scale parallel workloads in production Rails systems.

Full article here:

https://rubystacknews.com/2026/02/12/designing-safe-parallelism-in-rails/

#Ruby #Rails #Sidekiq #Performance #AWS #Scaling

Linking Ruby knowledge from the most remote places in the world.

Designing Safe Parallelism in Rails

Designing Safe Parallelism in Rails February 12, 2026 Eliminating Connection Pool Exhaustion in Production At Kaigi on Rails 2025, 片田 恭平 (@katakyo) delivered a deeply practical talk titled: “もう並列実行…
  • Copy link
  • Flag this post
  • Block
Giménez Silva Germán Alberto
Giménez Silva Germán Alberto
@gsgermanok@ruby.social  ·  activity timestamp 14 hours ago

When introducing parallelism in Rails,
the real danger isn’t threads.

It’s connection pool exhaustion.

Based on a Kaigi on Rails 2025 talk by @katakyo, I wrote a breakdown of how to safely scale parallel workloads in production Rails systems.

Full article here:

https://rubystacknews.com/2026/02/12/designing-safe-parallelism-in-rails/

#Ruby #Rails #Sidekiq #Performance #AWS #Scaling

Linking Ruby knowledge from the most remote places in the world.

Designing Safe Parallelism in Rails

Designing Safe Parallelism in Rails February 12, 2026 Eliminating Connection Pool Exhaustion in Production At Kaigi on Rails 2025, 片田 恭平 (@katakyo) delivered a deeply practical talk titled: “もう並列実行…
  • Copy link
  • Flag this post
  • Block
David B. :SetouchiExplorer: boosted
David B. :SetouchiExplorer:
David B. :SetouchiExplorer:
@David@setouchi.social  ·  activity timestamp last week

Can a #Mastodon specialist enlighten me?

Yesterday my host, @mastohost sent me an email to tell me that my media storage was full (which surprised me, especially because I very recently started automatically deleting my oldest posts to avoid just this). Today, rummaging through the admin, I found this very surprising graph in #Sidekiq
What could this be? Or is it the deletion of old posts that triggered that spike in processes? But if old posts have been deleted, why is the media storage full?

A graph showing a spike in processes, whatever that means.
A graph showing a spike in processes, whatever that means.
A graph showing a spike in processes, whatever that means.
  • Copy link
  • Flag this post
  • Block
David B. :SetouchiExplorer:
David B. :SetouchiExplorer:
@David@setouchi.social  ·  activity timestamp last week

Can a #Mastodon specialist enlighten me?

Yesterday my host, @mastohost sent me an email to tell me that my media storage was full (which surprised me, especially because I very recently started automatically deleting my oldest posts to avoid just this). Today, rummaging through the admin, I found this very surprising graph in #Sidekiq
What could this be? Or is it the deletion of old posts that triggered that spike in processes? But if old posts have been deleted, why is the media storage full?

A graph showing a spike in processes, whatever that means.
A graph showing a spike in processes, whatever that means.
A graph showing a spike in processes, whatever that means.
  • Copy link
  • Flag this post
  • Block
Stefano Marinelli
Stefano Marinelli
@stefano@mastodon.bsd.cafe  ·  activity timestamp 3 months ago

Some #BSDCafe #Mastodon #Sidekiq stats

Sidekiq Busy page showing 302017636 processed jobs, 9700663 failed, 5 busy, 0 enqueued, 3013 retries, 437 scheduled, 2684 dead. Status shows 3 processes, 65 threads, 5 busy threads, 8 percent utilization, 3711 MB RSS. Three processes listed: bsd_cmas01:44821 with 853 MB RSS, 25 threads, 0 busy; bsd_cmas01:50747 with 1827 MB RSS, 25 threads, 2 busy; bsd_cmas02:25091 with 1031 MB RSS, 15 threads, 3 busy.
Sidekiq Busy page showing 302017636 processed jobs, 9700663 failed, 5 busy, 0 enqueued, 3013 retries, 437 scheduled, 2684 dead. Status shows 3 processes, 65 threads, 5 busy threads, 8 percent utilization, 3711 MB RSS. Three processes listed: bsd_cmas01:44821 with 853 MB RSS, 25 threads, 0 busy; bsd_cmas01:50747 with 1827 MB RSS, 25 threads, 2 busy; bsd_cmas02:25091 with 1031 MB RSS, 15 threads, 3 busy.
Sidekiq Busy page showing 302017636 processed jobs, 9700663 failed, 5 busy, 0 enqueued, 3013 retries, 437 scheduled, 2684 dead. Status shows 3 processes, 65 threads, 5 busy threads, 8 percent utilization, 3711 MB RSS. Three processes listed: bsd_cmas01:44821 with 853 MB RSS, 25 threads, 0 busy; bsd_cmas01:50747 with 1827 MB RSS, 25 threads, 2 busy; bsd_cmas02:25091 with 1031 MB RSS, 15 threads, 3 busy.
  • Copy link
  • Flag this post
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.2-alpha.27 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct