Kilim: Fast, lightweight, cheap message passing in Java.

Channel:Google TechTalks · Length:45:10 · Published:2008-06-12 · Views:32841

Watch on YouTube

Summary

A Google Tech Talk by the author of Kilim, a Java library for lightweight actor-style message passing. It argues that message passing can replace shared-memory concurrency and claims performance competitive with or better than Erlang for huge numbers of actors.

Why HN recommends it

Pointed to as evidence that Java can do fast, cheap message-passing concurrency, as an alternative to Erlang or Scala actors.

Kilim's author did a nice Google Talk — HN, 2009

Functional programming · Software performance & optimization · Distributed systems

Subtitles (excerpt)

this is my friend SAS who's going to tell us about uh bringing message passing concurrency to Java if you've uh if you don't care about Java and have never had trouble with uh lock or threats maybe you're not in the Right audience I think I've said uh thanks ano um uh just as a brief uh note some of the techniques that I'm going to be talking about are I'm sure equally applicable to other imperative languages with pointers so although it says Java the framework that I've developed is for Java but many of the techniques are still more globally applicable and so I was working uh with ano and for the longest time in Industry uh developing highpe U uh high performance transactional Frameworks and the last thing that we did was write the web logic application server together and in all the uh pieces of software that I that we developed we ran into concurrency issues whether it is device drivers or you know uh middleware you run into U concurrency issues and there were a bunch of um problems that I wanted to tackle I keep running into these over and over again so as a background uh as we all know processors processing is getting increasingly distributed multiple cores per box multiple CPUs per box multiple boxes multiple data centers so a programmer not

On Hacker News

"Asynchronious message passing is old and great idea. Instead of synchronizing objects and dealing with deadlocks we try to isolate objects and let them exchange messages. Erlang proved it to be extremly powerful tool applicable to wide range of highly scalable mission critical applications. In JVM landscape big interest to this approach started after introducing Scala actors. " That statement is… — lucifer, 2010-02
Actors are decoupled from the means by which they are executed. Scala has a nice system where you can run thousands of event-based actors in a thread pool. It grows the pool as needed (as threads block). See [LINK] While it may use threads, Scala's actor system effectively allows you to create thousands of actors. Kilim is actually a pure (depending on whether you see a byte-code processing syste… — wynand, 2009-10
Erlang is a CSP system, first and foremost, and not actors. [CSP style concurrency on JVM]: [VIDEO] (Kilim, it should be noted, was benchmarked as scaling better than Erlang/OTP.) [LINK] (paper in top comment is worth the read.) Disclaimer: I think Erlang/OTP rocks. But JVM has its moments, as well, and in fairness has earned the "most advanced VM" title. — eternalban, 2012-04
SPEED :: In defence of Java, it is very quick when done right. See Kilim[1] for examples. SUPPORT :: On top of the speed Java has a supported hardware stack (Solaris). So if doing 100K connections is important to you, you can find engineers who can diagnose difficult problems on your whole stack. -------------- [1] [VIDEO] at 23:23 . Java is quick without Kilim too, this is just an example with s… — tezza, 2009-06

Related videos