joaoevangelista
While reading about on how execute long running NIFs on the VM I encountered the dirty schedulers option which seems familiar to me coming from a Java background, where some frameworks have a event loop for each processor and a pool for blocking stuff. Taking as a example a 4 core machine would let us have 4 schedulers for the BEAM, and some OS Threads as dirty schedulers, but using that approach isn’t going to put pressure on the BEAM schedulers? Would that cause any problems as the default NIIF approach or just lose capacity ?
PS: I can’t test it because of Windows problems
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 1- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
michalmuskala
If you have 4 cores with 4 schedulers and 4 dirty CPU schedulers, there are obviously cases where the OS kernel will switch to running the dirty schedulers. It’s done on the thread level, though, and OSes are generally good at making sure that all threads get their fair share of computing resources.