7 ms·
Erlang and IBM Power8 in the cloud: super-high single-system parallelism
- PhuFighter 12y agoInteresting simple cup test. I can't wait to see other, more comprehensive applications.
- desdiv 12y agoPrevious HN discussion: https://news.ycombinator.com/item?id=8481851 https://news.ycombinator.com/item?id=8481851
- dschiptsov 12y agoIt is not just about Erlang, but any language+runtime which has been designed upon a well-known set of sound principles (immutability, share-nothing, message-passing). As long as order of evaluation does not matter (for a pure-functional code) some [major] parts of a program could be evaluated in parallel by runtime without any changes in the code (especially when a high-order function composition - map/filter/reduce/etc is the primary pattern). So, Haskell, for example, will do it too.
- vinkelhake 12y agoHaskell will do what? Automatic parallelization of code? The big difference between Erlang and Haskell is that Erlang fundamentally encourages the programmer to think in terms of individual processes that communicate by message-passing. Programmers have also been taught that spawning processes is cheap so idiomatic Erlang code typically have tons of them.
- coolsunglasses 12y ago> Programmers have also been taught that spawning processes is cheap so idiomatic Erlang code typically have tons of them. The green threads in Haskell are just as cheap, in some cases, cheaper than Erlang's processes. Haskell programmers are similarly encouraged. Concurrency and parallelism are pretty easy in Haskell. http://chimera.labs.oreilly.com/books/1230000000929 http://chimera.labs.oreilly.com/books/1230000000929 http://hackage.haskell.org/package/slave-thread http://hackage.haskell.org/package/slave-thread
- dschiptsov 12y agoYes, indeed. Marlow's book is really good one.
- felixgallo 12y agoI love my haskell brethren dearly, but haskell isn't organized structurally around an essentially-mandatory fundamentally concurrent, debuggable, quasi-preemptive core like OTP. Not that it won't get there eventually (cf. Cloud Haskell) but it's more than just being able to run concurrent threads. Note: this is not a language flame, just a personal opinion/observation, and I love and welcome correction.
- coolsunglasses 12y agoHaskellers like to pick and choose their abstractions. That's why we have MVar and TVar (STM) and IVar and locks/semaphores and unbounded channels and bounded channels and software transactional channels and green threads and Async and OS threads… You're going to see what Erlang did atomized, implemented piecemeal, and reconstructed. Cloud Haskell burnt too much goodwill in pursuit of a mostly pointless feature. That's how we ended up with slave-thread…the beginnings of supervisor trees. Haskellers would rather pick and choose. It's worked well so far.
- saosebastiao 12y agoLet us know when you get to 9-nines on a distributed application.
- dschiptsov 12y agoYou are right. Haskell is an academic research vehicle while Erlang is a pragmatic "industry-strength" (i hate these buzzwords, but they are useful generalizations) functional language. In theory, we could re-write almost any part of OTP in Haskell, in practice, however, "runtime is hard" and the biggest selling point of Erlang is that its runtime and standard library (OTP) has been evolved for almost 20 years and is based on the same principles of a functional language (except, perhaps lazyness by default) as Haskell. In other words, while Haskell is a "playground for researches of type theory in context of programming languages and compilers" Erlang/OT is a "telecom industry-standard toolkit". A close analogy, in my opinion, could be the pair of Scheme/Racket and CL. The first was mostly an academic teaching and research tool, while second is a pragmatic (but unfortunately bloated) tool-set.
- dragonwriter 12y ago> So, Haskell, for example, will do it too. By "will do it" you mean "would, in theory, support a compiler that parallelized significant amounts of idiomatic code with no source changes"? Maybe. I don't think any existing Haskell compiler does that, though.
- wyager 12y agoI've had GHC automagically parallelize tree-traversal code before. However, I think in general you have to put a bit of work in to it. Of course, you could theoretically just write an actor library that did the exact same thing as erlang.
- throwaway_yy2Di 12y agoHow does POWER8 compare to x86, e.g. Haswell? Just skimming some of the architecture details... * 4x hardware threads per core (8-way SMT vs. 2) * 1/4th FP throughput per core (8 SP flops/cycle vs. 32) * 3x bandwidth to RAM (230 GB/s vs. 68) [edit: updated for Haswell-EP] https://en.wikipedia.org/wiki/POWER8#Specifications https://en.wikipedia.org/wiki/POWER8#Specifications http://www.redbooks.ibm.com/abstracts/tips1153.html http://www.redbooks.ibm.com/abstracts/tips1153.html What is it good for?
- jacques_chester 12y ago> What is it good for? Running very demanding single-system software. It's the sort of box you'd install DB2 or Oracle on, especially if you've already tied your business to IBM solutions in the past.
- PhuFighter 12y agoIt depends on what you mean by "demanding". I think that single threaded applications on x86 (with nothing else running) will smoke the Power8 system. But if you have lots of threads and high levels of concurrency going on, i think that the results will be very much workload dependent.
- Marat_Dukhan 12y ago+ Hardware Transactional Memory that isn't buggy
- benjarrell 12y agoBased on experience with POWER7, emptying your wallet.
- PhuFighter 12y agoit's surprising how much cheaper these Power8 boxes are compared to the Power7 boxes. You can get a tyan 2U, 1 socket system for $2800 FOB HK: http://www.tyan.com/campaign/openpower/ http://www.tyan.com/campaign/openpower/
- jacques_chester 12y agoFor those as confused as I was at first, the critical line is "total time". 2.8s for the P8 vs 38.7s for the x86. Otherwise the x86 comes out looking a lot better -- lower 95th percentile, lower max, lower average. (Modulo usual complaints about benchmark porn: single run, lack of standard deviation, unknown configuration differences etc etc).
- baq 12y agothanks for the explanation, had major cognitive dissonance about that post.
- felixgallo 12y agoyeah, sorry, it was just a quick test; I didn't even run any erlang besides building it from scratch, starting it up and seeing that BEAM recognized the right number of schedulers. It would be interesting to run a more comprehensive test suite than a single timing run, for sure.
- throwawayaway 12y agoYour post should be voted top, it's the most informative. I've spent the whole day scratching my head. The power8 confusion in many ways reminds me of the p4 netburst architecture, not architecturally in any way, but in the sense that "when they are good they are really good". But both by and large are not any great shakes.
- neurotixz 12y agoWhile the performance seen here is nice, i'm curious to see the price/performance ratio. Running against a 8-core XEON would not make sense if the closer Intel system price-wise is a quad 12-core xeon... Obviously we are talking cloud here so it might not even apply. By my experience with Power7, the price/performance ratio is much lower on Power then Intel systems. Maybe it changed but i'm not holding my breath, even if IBM seems much more aggressive on pricing with P8 then they were with P5-P7. The Quick calculation, absolutely unscientific: Seeing that the price is 0.14$/hour for the 6-core xeon and 1.08$/hour on the 176 core P8, it would have to be roughly 8-10x faster to justify the cost difference, not sure it will be the case.
- felixgallo 12y agothe thing you're getting here is primarily throughput on a single image. Even if it's more expensive per-core per-hour, you can't discount that you'd have to work a lot harder to get the equivalent 30-box distributed solution to work properly, and even then it would have certain disadvantages owing to network latency.
- nonsequ 12y agoThis is interesting and I'd like to hear more opinions on it. My impression is that distributed computing has been eating Power/Sparc/Z processors' lunch for a long time now because software has made up for the deficiencies of coordinating 30 boxes. Do you and do any others believe that we are at an inflection point where the pendulum swings back in the direction of 'high-performance' processors like Power8, or will improvements in 'scale-out' ease-of-use and economies of scale continue to win the day?
- jacques_chester 12y agoIf you have a problem that behaves poorly in the face of the Network Fallacies, then you want to scale vertically. RDBMSes are a classic example. Some kinds of compute-heavy problems too -- simulations with lots of coupled components, video compression etc.
- 12y ago
- Erwin 12y agoA while ago (here's an article from 2002: http://lwn.net/Articles/6367/ http://lwn.net/Articles/6367/ ), the big new thing was going to be ibm mainframes running linux VMs. Whatever became of that? Is anyone still doing that?
- PhuFighter 12y agothe last I heard, Linux on the IBM Mainframes were driving > 50% of their sales.
- rodgerd 12y agoMy employer does. Plenty of large companies with an existing Z footprint do.
- rodgerd 12y agoMy employer does. Plenty of large companies with an existing Z footprint do.
- listic 12y agoWhich one is that plan that allows you to "spend about $1"?
- deleted 12y ago[deleted]
- felixgallo 12y agohttps://cloud.runabove.com/login/?launch=power8 https://cloud.runabove.com/login/?launch=power8 leads to the power8 pages. Not a super well organized site imo.