Thanks, i added this plugins, and test it on production, it still works.
i use sequel_pg and pg gem on production, and change web server from puma to falcon. so, can you please tell me if there exists some special log or somethings to prove current work on per-fiber request mode? 在2021年10月25日星期一 UTC+8 上午2:16:09<Jeremy Evans> 写道： > On Sat, Oct 23, 2021 at 9:24 AM Billy Zheng <[email protected]> wrote: > >> Ruby 3.1 will make ruby fiber scheduler, which introduced in ruby 3.0, >> the official non-block io and concurrency solution, more mature and >> completely, but, as mention by Samuel Williams @ioquatix, who is the >> author of async, in this video. >> >> https://youtu.be/Y29SSOS4UOc?list=LL&t=1406 >> >> activerecord use one connection per thread, because of this, multiple >> independent fiber >> on the same thread will be using the same underlying connection, this can >> cause problems because multiple fibers could incorrectly share a >> transaction, this is kind of a design fault of activerecord. >> >> so, i just curious if sequel exists a similar issue, and if is, if there >> is a plan to solve this, and how to do it. >> > > You can use the fiber_concurrency extension to support this in Sequel: > https://sequel.jeremyevans.net/rdoc-plugins/files/lib/sequel/extensions/fiber_concurrency_rb.html > > Thanks, > Jeremy > > > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/2c8fd9e3-c771-4358-b6d0-59ce60bfa425n%40googlegroups.com.
