Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

105
Views
Erlang Socket at OS Level

I am so confused about multi-thread networking. Since a Socket is an OS Level structure, handling sockets at Erlang BEAM VM level has an equivalent at OS Level, and there are multi options to handle parallel connections by OS-Threads (select, poll, epoll,....) and that depends of the OS but what i can't understand and I searched a lot about without any answer is: If we have 4 Parallel Erlang processes listen to accept connection on one Socket, what is the equivalent at OS Level? 4 waiting Parallel OS-Threads? N Parallel OS-Thread?

over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

It's a difficult correspondence to draw. Your suggestion 4 Parallel threads is probably the closest equivalent. Things get a bit harder to pin down because a kernel thread will likely take up more system resources than each process. Threads typically share memory space while there is memory protection between processes. So it depends on how far you want to take the simile, but basically there will be 4 separate lines of processing blocked on I/O.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!