Skip to content
HN On Hacker News ↗

Release v1.6.0 - fiber execution mode (with Async) · rails/solid_queue

▲ 104 points • 39 comments • by earcar • 3mo ago • HN discussion ↗

Pangram verdict · v3.3

We believe that this entire text is human-written.

0 %

AI likelihood · overall

Human
100% human-written 0% AI-generated
SEGMENTS · HUMAN 1 of 1
SEGMENTS · AI 0 of 1
WORD COUNT 167
PEAK AI % 0% · §1
Analyzed
Aug 1
backend: pangram/v3.3
Segments scanned
1 windows
avg 167 words each
Distribution
100 / 0%
human / AI fraction
Verdict
Human
Pangram v3.3

Article text · 167 words · 1 segments analyzed

Human AI-generated
§1 Human · 0%

A long-awaited feature thanks to @crmne on this release: instead of using a thread pool to run jobs in multiple threads per works, you can now use fibers on a single fiber reactor thread. To use this, you just need to specify the number of fibers instead of the number of threads in your worker configuration, like this: workers: - queues: "api*" fibers: 100 polling_interval: 0.05 It uses Async under the hood, so you need to have that as a dependency for it to work. Also, you need to be using fiber isolation in Rails (config.active_support.isolation_level`` = :fiber). This can be very useful for I/O-bound workloads, such as those involving LLM calls. What's Changed Add fiber worker execution mode by @crmne in #728 Roll back transactions leaked by killed job threads in tests by @rosa in #773 Document how to update dynamic recurring tasks by @wintan1418 in #777 New Contributors @crmne made their first contribution in #728 @wintan1418 made their first contribution in #777 Full Changelog: v1.5.1...v1.6.0