thoughtarray
Doing something as "at the same time" as possible
I know beam makes a scheduler per CPU (OS thread); so theoretically I can do something at exactly the same time up to the number of CPUs I have.
What is the best way to kick them all off at the same time? Is my only option to send (via Process.send or Kernel.send) a message to a process running on each scheduler? If I do that, the messages are sent out serially. Any alternative techniques or should that be considered fast enough in this ecosystem?
I posted a similar post, but I think it was too complex to bother with.
Most Liked
benwilson512
The type of question you’re asking I think requires some definitions. There is, at the end of the day, no such thing as truly “at the same time” there is “measured to be within a time bound by an observer”. How tight does the time bound need to be? Why? Who is observing this?
schneebyte
You could check how others are doing it.
Maybe you could tell your processes to start at a specific point in time
then just have them sleep and check time repeatedly.
/one more thing
I don’t think you can choose the specific scheduler a process is on.
:erlang.system_info(:scheduler_id)
I guess if you spawn enough processes under load it should be spread out to all available schedulers.
Last Post!
thoughtarray
Thanks for the replies, all!
@benwilson512, I think the context you might be seeking is in the linked original post. That post didn’t gent any replies; so I made this post much shorter and simpler. By “at the same time”, I mean parallelism. The goal is to squish that time bound as much as possible in BEAM. I know for other languages the solution would be to start a thread per CPU core.
@al2o3cr, yeah, I think my desires are leaving the realm of practical and entering theoretical (at least in BEAM land). I do have a desire for that TCP SYN to drop in on server/listener to be parallel as possible in BEAM land. Insofar as your recommendation, it’s totally the practical way to do it and may end up what I do if I can’t find what I’m looking for.
@schneebyte, I have seen stressgrid, but not the others. Thanks for the links! I had considered a timer-based kick-off, but wasn’t sure the best way to do it in Elixir/Erlang since I was under the impression that time was pretty squishy in BEAM land.
Regarding choosing specific schedulers, I thought PartitionSupervisor would help partition its children across schedulers. Do I have that messed up in my head?
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Develop your skills with books, videos, and courses.
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
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security
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 for Elixir devs who love to ship. Start your free account.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"