Use async nifs technique to avoid blocking the BEAM's schedulers #1
Loading…
Reference in a new issue
No description provided.
Delete branch "gsb-async-nifs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Running more than a simple amount of code on a scheduler thread turns out to be a very bad idea for R15 and later versions of the BEAM. Here we use a thread-pool to execute work after being queued on the scheduler thread. By placing more long-running tasks onto non-scheduler threads we lower the chances of confusing the Erlang scheduler and in so doing hopefully avoid having stalled scheduler threads.
This is no longer relevant, gsb-async-nifs3 is where you'll find the functional async branch and here's the pull request for those changes. https://github.com/basho-labs/wterl/pull/6
Pull request closed