3 ms·
Very interesting and accessible! One comment on terminology... The people who pay the most attention to the topic maintain a distinction between parallelism an
by ncmncm 6y ago
Very interesting and accessible!
One comment on terminology... The people who pay the most attention to the topic maintain a distinction between parallelism and concurrency. Parallelism is more than one bit of work getting done at a time. Concurrency is about coordinating everything being done to ensure that the results make sense.
They say "parallelism giveth, concurrency taketh away". Work done on concurrency is overhead, not directly producing results. Sometimes it makes less useful work be done, such a stalling a functional unit while another uses a shared bus, or delivering two results A, B produced in random order in the required order.
Parallelism is associated with the "data plane", concurrency with the "control plane", in systems that use those ideas.
Software people often don't know about the distinction, and use the terms interchangeably. Keeping them distinct helps sharpen thinking about systems affected by it.
- rrss 6y ago> Software people often don't know about the distinction, and use the terms interchangeably I think YMMV here - in my experience, only (some) software people make this distinction, and hardware people use the terms interchangeably.
- ncmncm 6y agoUsing the distinction gives you a superpower.