-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable dirty-scheduler on default erlang image #29
Comments
also --enable-dirty-schedulers will become default for #29 for Erlang19.
also --enable-dirty-schedulers will become default for #29 for Erlang19.
another good one: https://medium.com/@jlouis666/erlang-dirty-scheduler-overhead-6e1219dcc7 |
also --enable-dirty-schedulers will become default for #29 for Erlang19.
Thanks for the links and for updating the image. Waiting for #29. About the dockerhub comments, understood. |
Hi there, I was wondering if you know when this will be merged? Having dirty schedulers enabled in the Erlang 19 image would greatly simplify my other image(s). Thanks! |
sorry didn't have a chance to update, while doing #32 I did some local test of enabled dirty scheduler, it works without too much effort; so another PR to enable dirty scheduler should be there shortly |
Hi! This is great to hear. Looking forward to trying out the new image. Thanks! |
- add support for observer as the most popular wx GUI based app for #28; image size increased ~65MB. REPOSITORY TAG IMAGE ID CREATED SIZE otp 20.0-rc0-cd48b81-wx f8b3e0fc15dd 49 seconds ago 814.9 MB otp 20.0-rc0-cd48b81 dbff7d029fed About an hour ago 749.9 MB - also support dirty scheduler for #29; - temporarily disable compiling rebar3 because it fail bootstrap on Erlang 20; see more in erlang/rebar3#1414
I just found a comment on the docker hub page https://hub.docker.com/_/erlang/
and researched somewhat for benefits why need dirty scheduler and how to do that
https://news.ycombinator.com/item?id=11064763
https://hamidreza-s.github.io/erlang/scheduling/real-time/preemptive/migration/2016/02/09/erlang-scheduler-details.html
http://erlang.org/doc/installation_guide/INSTALL.html#Advanced-configuration-and-build-of-ErlangOTP_Configuring
the good news is this feature would be an easy one https://github.com/c0b/docker-erlang-otp/blob/master/19/Dockerfile#L24 just need some sanity check before releasing in the new way of building 19+ images
(generally a github issue for feature request is preferred over docker hub comment, because hub.docker.com doesn't have comments notification and many other features as a discussion board should have)
The text was updated successfully, but these errors were encountered: