Use async nifs technique to avoid blocking the BEAM's schedulers #1

Closed
gburd wants to merge 15 commits from gsb-async-nifs into master
gburd commented 2012-11-30 02:25:31 +00:00 (Migrated from github.com)

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.

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.
gburd commented 2013-04-19 16:56:43 +00:00 (Migrated from github.com)

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

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

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: greg/wterl#1
No description provided.