‹ BackHN Continuity

Thread

Book review: Is parallel programming hard, and, if so, what can you do about it?

149 points · 66 comments · ahelwer

  1. criddell · · focus · HN ↗
    This review seems to equate parallelism and concurrency as the same thing and they are not.

    As I understand it, the parallelism is about task execution and concurrency is about task structure. Or, as Rob Pike said:

    "Concurrency is about dealing with lots of things at once. Parallelism is about doing lots of things at once."

    He said that in his Concurrency is not Parallelism talk.

    1. mkehrt · · focus · HN ↗
      As other comments have pointed out, this is just not true in general usage.

      When I was a grad student studying this stuff (~20 years ago), we used "parallelism" to mean running on different cores at the same time and "concurrency" to mean preemptive multithreading on a single processor.

      1. wiml · · focus · HN ↗
        That's the same distinction, made in the same way, isn't it?
        1. mkehrt · · focus · HN ↗
          Well, we were using it to talk about things like cache invalidation and lax memory models rather than properties of algorithms.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.