Does Puma plugin create one supervisor process per Puma process?

Open
#802 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
ruby, sqlite
Domain
backend, databases

Research direction

Start by locating the Puma plugin's supervisor and process-handling entry points, then trace how supervisor processes relate to configured Puma processes and threads. Confirm the behavior using any existing tests or a minimal reproduction with SQLite; done means providing a definitive explanation of the process relationship and its relevance to database locking.

Written by the indexing model from the issue text.

Description

Or does it create one supervisor process regardless of the number of Puma processes?

I think it's the latter but I'd appreciate a definitive answer :)

(I'm trying to tune my processes and threads to avoid SQLite3::BusyException: database is locked errors.)

Sorry if this is the wrong place to ask questions; I couldn't see a discussions tab or anything similar.

Thank you!

Dominant language
Ruby
Stars
2.5k
Forks
250
Avg merge
7h 7m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rails/solid_queue

All issues in rails/solid_queue

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.