Cb0dap8zt52glyed7qyi
SkillsCast

GPars 2014

11th December 2014 in London at Skills Matter

There are 19 other SkillsCasts available from Groovy & Grails eXchange 2014

Please log in to watch this conference skillscast.

Https s3.amazonaws.com prod.tracker2 resource 41088130 skillsmatter conference skillscast o9nohu

GPars is the standard package for high-level concurrency and parallelism in Groovy: although it is a separate project and artefact, it is distributed as standard in Groovy. There are (at least) two forms of concurrency and parallelism: single computer (multi-core, multi-processor) and cluster. Since it's inception, GPars has focused on single computer, indeed single JVM activity. 2014 has seen a significant change: in a Google Summer of Code 2014 project, Rafał Sławik took the cluster concurrency and parallelism code that was in the GPars and amended and extended it so that it worked.

In this session, we will take a quick (practically based) survey of existing GPars to set the context, and then look (using examples) at the core of the new features. We will almost certainly try and play a small game – network willing.

YOU MAY ALSO LIKE:

Thanks to our sponsors

GPars 2014

Russel Winder

Russel is an ex-theoretical physicist, ex-UNIX system programmer, ex-academic, ex-independent consultant, ex-analyst, ex-author, ex-expert witness and ex-trainer. Russel is still interested in programming and programming languages, and all things parallel and concurrent. And build. He's actively involved with GPars, Me TV, and various bits and pieces of SDR. Russel likes working with Python, Ceylon, Kotlin, D, Go, Rust, and C++17.

SkillsCast

Please log in to watch this conference skillscast.

Https s3.amazonaws.com prod.tracker2 resource 41088130 skillsmatter conference skillscast o9nohu

GPars is the standard package for high-level concurrency and parallelism in Groovy: although it is a separate project and artefact, it is distributed as standard in Groovy. There are (at least) two forms of concurrency and parallelism: single computer (multi-core, multi-processor) and cluster. Since it's inception, GPars has focused on single computer, indeed single JVM activity. 2014 has seen a significant change: in a Google Summer of Code 2014 project, Rafał Sławik took the cluster concurrency and parallelism code that was in the GPars and amended and extended it so that it worked.

In this session, we will take a quick (practically based) survey of existing GPars to set the context, and then look (using examples) at the core of the new features. We will almost certainly try and play a small game – network willing.

YOU MAY ALSO LIKE:

Thanks to our sponsors

About the Speaker

GPars 2014

Russel Winder

Russel is an ex-theoretical physicist, ex-UNIX system programmer, ex-academic, ex-independent consultant, ex-analyst, ex-author, ex-expert witness and ex-trainer. Russel is still interested in programming and programming languages, and all things parallel and concurrent. And build. He's actively involved with GPars, Me TV, and various bits and pieces of SDR. Russel likes working with Python, Ceylon, Kotlin, D, Go, Rust, and C++17.

Photos