Fork/Join for Fun and Profit!
Upcoming SlideShare
Loading in...5
×
 

Fork/Join for Fun and Profit!

on

  • 1,757 views

This session was presented at the JFall 2011 conference in The Netherlands. It introduces the Fork/Join framework that was introduced in Java 7. Example code can be found at ...

This session was presented at the JFall 2011 conference in The Netherlands. It introduces the Fork/Join framework that was introduced in Java 7. Example code can be found at http://bit.y/jfall-forkjoin

Statistics

Views

Total Views
1,757
Slideshare-icon Views on SlideShare
1,754
Embed Views
3

Actions

Likes
2
Downloads
29
Comments
0

2 Embeds 3

http://a0.twimg.com 2
http://us-w1.rockmelt.com 1

Accessibility

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Sander Mak, Info Support\nGaan het hebben over Doug Lea’s fork/join (al sinds 1998 in the works), nu onderdeel van Java7\nFun & Profit: profit vanwege snellere apps, fun hangt van je interesses af :)\n
  • No choice but to churn on each task sequentially\nPentium 5, 3.4Ghz -> hitting physical limits! (approach: speed, smarter instructions onchip)\nThreading alleviates IO contention, not CPU contention\n
  • No choice but to churn on each task sequentially\nPentium 5, 3.4Ghz -> hitting physical limits! (approach: speed, smarter instructions onchip)\nThreading alleviates IO contention, not CPU contention\n
  • More cores, lower speed. Do nothing -> your app could be slower! Embrace parallelism.\nIn webapps we get a lot of request-oriented parallelism for free.\nWhat about other applications/algorithms?\n
  • CPU architectures changed all the time without having to change Java code... why is this different? -> Implicit data-dependencies in code (also, shared memory/state problems)\n
  • Builds a tree with explicit dependencies between tasks!\nDivide-and-conquer algorithms\nHier: 6 fork acties, 6 join acties\n
  • Threshold is key: overhead vs. effective work per unit\nApplicable to for example:search, sort, aggregating data\n
  • ForkJoinTask is a future\n
  • - getAvailableProcessors on System.runtime\n- possible to set own size (e.g. restrict to 4 of n cores)\n
  • \n
  • \n
  • - forked tasks pushed on top local deque\n- idle worker steals from bottom deque of other worker -> prevent contention on deque, and largest tasks get stolen!\n- no work stolen? eventually yield workerthread. Typ. 0-2% stolen\n- Workstealing == loadbalancing without central coord!\n
  • Fibonacci in het begin bekeken. Allemaal reken-intensief.\nSprekend voorbeeld: password hashes tegen rainbow table aanhouden.\n
  • Still threads are better when doing blocking I/O networking etc.\n
  • \n
  • F/J: recursively apply same task, M/R: apply different map/reduce steps, not necessarily recursive (but could happen)\n
  • \n
  • Websphere staat bv ook geen threadcreatie in servlet toe\nEvt. JCA adapter noemen\n
  • \n
  • \n
  • \n
  • needs lambdas!\nbut already available in jsr166y with anonymous inner classes\n
  • \n

Fork/Join for Fun and Profit! Fork/Join for Fun and Profit! Presentation Transcript

  • Fork/Join for Fun and Profit! @Sander_Mak
  • What is the problem anyway?
  • What is the problem anyway?
  • What is the problem anyway?
  • What is the problem anyway?‣ So let the Compiler figure out the hard stuff! if (n < 2) n else fib(n - 1) + fib(n - 2) n < 2 n‣ Or maybe not ...
  • Fork/Join in picturesFork:Recursively decompose Resultlarge task into subtasks Task 1Join: Task 2 Task 3Await results ofrecursive tasks Task 4 Task 5 Task 6 Task 7and combine
  • Fork/Join in pseudocodecompute(problem) {  if (problem.size < threshold)    directlySolve(problem)  else {    do-forked { leftResult = compute(left(problem)) rightResult = compute(right(problem)) }    join(leftResult, rightResult)    return combine(leftResult, rightResult)  }}
  • ForkJoinPoolIntroducing:  java.uCl.concurrent.ForkJoinPool ForkJoinTask  java.uCl.concurrent.ForkJoinTask RecursiveAction RecursiveTaskForkJoinPool:void execute (ForkJoinTask<?>)T invoke (ForkJoinTask<T>)ForkJoinTask<T> submit (ForkJoinTask<T>)  
  • ForkJoinPoolIntroducing:  java.uCl.concurrent.ForkJoinPool Worker 1‣ Implements ExecutorService‣ Autosizing workers Worker 2‣ Double‐ended queue‣ Workstealing algorithm Worker 3  
  • Sorting demoMergesort
  • ForkJoinTasks‣ 100 < ‘basic computaConal steps’ < 10.000‣ Acyclic, typically decreasing in size‣ Join doesn’t block thread!‣ Do:  ‣ OpCmize sequenCal threshold ‣ Share, don’t copy input (task locality)‣ Don’t: ‣ Synchronize/lock (but use: Phaser) ‣ Do blocking I/O
  • Work stealingWorker 1 Worker 2 Worker 3 ForkJoinPool
  • Speedups
  • What about threads?‣ Heavyweight (try starCng a million)‣ Implicit dependencies between tasks ‣ Manual synchronizaCon ‣ Deadlock/livelock/race condiCons‣ Hard to scale to available parallelism
  • Pooling/ExecutorService then?‣ ForkJoinPool implements ExecutorService‣ Coarse‐grained independent tasks‣ Recursively decomposed tasks spend most Cme  waiCng ‣ In normal threadpool: starvaCon‣ Task‐queue of threadpool‐backed ExecutorService not  opCmized for many small tasks‣ No workstealing
  • Map/Reduce?Environment Single JVM ClusterModel Recursive forking O^en single mapScales with Cores/CPUs NodesWorker Workstealing No inter‐node interacDon communicaCon
  • DemoSony’s been hacked... Are we compromised...?
  • Fork/Join and‣ ForkJoinPool starts threads ‣ Illegal in EJBs ‣ Fair game in servlets/CDI beans‣ Don’t create ForkJoinPool for each request‣ Idea: WorkManager to create poolthreads‣ Single pool, async submit(ForkJoinTask) ‣ Don’t Ce up request thread: Servlet 3.0
  • Alternatives outside Java?‣ Actors‣ So^ware transacConal memory‣ Dataflow concurrency‣ Agents‣ ... Some of this built on F/J Akka GPars
  • Criticism‣ ImplementaCon too complex (uses Unsafe)‣ Some assumpCons quesConable ‣ 1‐1 mapping workerthread/OS thread ‣ Workstealing best opCon?‣ Scalability 100+ cores?
  • Future GPU? Java 8 OpenCL? Java 7 Parallel Java 5 Collections Fork/JoinJava1.0 - 1.4 - j.u.concurrent: high-level locks, concurrent coll.- threads- synchronized- volatile
  • Futureint scanLog(List<String> lines, String query) { Pattern p = ... return lines.parallel() .filter(s => p.matcher(s).matches()) .count();}
  • ForkJoinPool.shutDownNow() Questions?Code @ bit.ly/jfall-forkjoin