Solid Queue 1.6.0 has been released, introducing a new fiber worker execution mode. This feature allows users to configure workers to utilize fibers on a single fiber reactor thread, moving away from the previous thread pool model for running jobs.
To enable fiber workers, users need to specify the number of fibers in their worker configuration instead of threads. The implementation relies on Async, which must be included as a dependency. Additionally, Rails applications must be configured to use fiber isolation (config.active_support.isolation_level = :fiber).
The new fiber worker mode is particularly useful for I/O-bound workloads. This includes tasks such as making calls to Large Language Models (LLMs), where the application spends significant time waiting for external operations to complete. Fibers can improve efficiency in these scenarios.
Beyond fiber worker support, Solid Queue 1.6.0 also includes a fix to roll back transactions leaked by killed job threads in tests and documentation updates for managing dynamic recurring tasks. These updates contribute to the overall stability and usability of the queueing system.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
Solid Queue version 1.6.0 now supports fiber workers, allowing jobs to run on a single fiber reactor thread instead of a thread pool. This change is beneficial for I/O-bound workloads, such as those involving LLM calls, by improving efficiency.