Primitive Concurrency in Elixir

Transcript

1. Primitive Concurrency in Elixir
2. Timeline 1 2 3 4 Primitive Concurrency Generic Server Data Processing Actor Model We’re here
3. So, what are we gonna tackle now?
4. Concurrency Concurrency & Concurrency vs Parallelism 01 The VM & Processes Erlang is about writing high available systems - system that runs forever 02 Server Process An informal name for process that runs for a long time(or forever) 03 Runtime Considerations Some internal considerations about the BEAM 04
5. Who am I? Randson! I’m a software engineer, Writer, video editor. Interested in cartoon draw. - Back-end with Elixir; - Increasingly learning. Trying to make the world a better place to live, through technology.
6. Concurrency 01. Basic of Concurrency & Parallelism
7. Although they’re often used interchangeably, concurrent and parallel refer to related but different things. Concurrent or Parallel?
8. A concurrent program has many thread of control. These threads may or may not run in parallel. Related but Different
9. A parallel program may or may not have more than one logical thread of control. Related but Different
10. — Rob Pike Concurrency is about dealing with a lot of things at once. Parallelism is about doing a lot of things at once.
11. Concurrency & Parallelism are often confused because traditional thread and lock doesn’t directly support parallelism Beyond Sequential Execution
12. If you want to exploit multiple cores with thread and locks. Your only option is to create a concurrent program and then run it in a parallel hardware. Beyond Sequential Execution
13. Concurrent programs are often nondeterministic. They will give different results depending on the precise timing of events. Beyond Sequential Execution
14. Parallelism, by contrast, doesn’t necessarily imply nondeterminism. Languages that supports allows you to write parallel code without introducing the specter of nondeterminism. Beyond Sequential Execution
15. Concurrent How to Illustrate? Concurrent & Parallel Parallel
16. Concurrent What’s concurrency? And Parallelism(only)?
17. Concurrent & Parallel Elixir track Erlang track
18. Parallel Every is student is assigned to do a five christmas card!
19. — Rob Pike Concurrency is about dealing with a lot of things at once. Parallelism is about doing a lot of things at once.
20. Concurrency is not parallelism Explains the difference with Go channels examples. https://www.youtube.com/watch?v=oV9rvDllKEg
21. Processors have stopped getting faster. Using new hardware doesn’t mean you program will be fast. These days, if you need more performance, you need to exploit more processors and that means exploiting parallelism. These aren’t new, why so hot now?
22. Not at all. It allows you to create software that’s responsive, fault-tolerant, multi-region, and(if you’re in the right approach) simpler than traditional sequential software. Is it just about exploiting multiple cores?
23. Concurrent software for a concurrent world Beyond multiple cores
24. Distributed software for a distributed world Beyond multiple cores
25. Resilient software for a unpredictable world Beyond multiple cores
26. Simple software for a complex world Beyond multiple cores
27. Models 1 2 3 4 Threads & Locks Actors CSP Lambda And others…
28. It’s everywhere. Even client-side web programming is concurrent. I hope this talk can help you understand concurrency. ;) How will this affect me?
29. So, what about Elixir?
30. The VM & Process 02. Erlang is about writing high available systems - system that runs forever
31. What BEAM stand for? Is the Virtual Machine(VM) at the core of the framework Erlang Open Telecom Machine(OTP) It stands for Bjorn’s Erlang Abstract Machine. The predecessor of the BEAM was JAM and stands for Joe’s Abstract Machine(JAM). Created by Joe Armstrong.
32. High Availability To have a system that “runs forever” we have to tackle some things first: - Fault-Tolerance - Scalability - Distribution
33. Fault-tolerance Minimize, isolate, and recover from effects of runtime.
34. Scalability How to handle high load of data without re-deploying our code?
35. Distribution We can run our app in multiple machines(even if the machine isn’t in our continent).
36. Fault-tolerant How to achieve HA? Scalability Distribution
37. High Availability If we address these challenges, our systems can constantly provide service without downtime. Concurrency play an important role here. In BEAM, the unit of concurrency is a process.
38. Don't confuse BEAM process with OS process!
39. BEAM CPU/Scheduler OS Thread CPU/Scheduler OS Thread CPU/Scheduler OS Thread CPU/Scheduler OS Thread Process Process Process Process
40. BEAM Process Lightweight & Cheap OS Process Heavy & deals with more things
41. Process The basic concurrency primitive is called Erlang process. A typical erlang VM can run thousands or even millions of process. It only uses the available CPU cores, parallelizing execution as much as possible.
42. Process - Fault Tolerance They (processes) are completely isolated from each other. They don’t share any memory with another process running inside the VM. If something bad happens, it has only a local impact.
43. Process - Scalability Process communicate via asynchronous messages. A typical system in Erlang can be divided into a large number of concurrent processes. Erlang system is scalable because they can take advantage of all CPU.
44. Process - Distribution Communication works the same way regardless of where they were born. Process have a “mailbox” in which they can process messages inside. The mailbox is just a queue of messages inside of a process.
45. Process As you can see, concurrency is a crucial element in Erlang. With I/O operations happening, the VM delegates to separate threads/service the execution, not blocking it.
46. Erlang in Action
47. Server Process 03. Is Flow, GenStage or Broadway a choice to process data?
48. It’s common to have long-running process A simple process can serve millions of requests An informal name for a process that run for a long time (or forever) Server Process
49. Make use of endless tail recursion Not a problem for a function that run itself forever To implement a server process, you just need an endless loop Server Process
50. defmodule ServerProcess do def start, do: spawn(&loop/0) def loop do # process the message loop() end end
51. Keep a process internal state update while it’s alive Process messages coming from calls Messages are always sequential Server Process - You can:
52. pool = Enum.map(1..100, fn -> ServerProcess.start() end) Server Process
53. Each process has its own state They communicate with each other by messages You can have both mutable and immutable states Server Process - You can:
54. But be aware! Processes can fail and die
55. They’re isolated, so it’s not a problem for other processes currently running inside the VM Without proper treatment, the process dies losing its internal state Server Process
56. Which guides us to?
57. Runtime Considerations 04. Internal considerations about the BEAM
58. Runtime considerations Despite being the best type of concurrency, it still has some flaws The mailbox of a process may become a bottleneck which affects the overall throughput Maybe the flaws are related to how you organize your supervision tree
59. Runtime considerations A mailbox size of a process is limited by available memory If a process constantly falls, the mailbox will continuously increase causing a crash to the application Larger mailboxes can significantly affect performance.
60. Runtime considerations Always try to create a process that handles one thing alone
61. Thanks! Do you have any questions? orandson@gmail.com — https://rands0n.com
62. References - https://medium.com/platform-engineer/understanding-jvm-architecture-22c0ddf09722 - https://msdeep14.github.io/diff-os-erlang-process/ - https://www.manning.com/books/elixir-in-action-second-edition - https://pragprog.com/titles/pb7con/seven-concurrency-models-in-seven-weeks/
63. Thanks! orandson@gmail.com — https://rands0n.com