Panel with Ben Sless and Léo Noel
summary
Practical profiling advice: wait until an app exists, then generate flame graphs (use VisualVM and Brendan Gregg’s materials) and use Criterium for focused microbenchmarks; expect a learning curve interpreting async profiler output. Missionary offers a supervised, effect-based alternative to core.async with production intent but known edge-case bugs tracked in GitHub; its sweet spots are UIs with fine-grained reactivity and distributed algorithms. SIMD via JDK16 vectors helps numeric hotspots but rarely maps directly to Clojure collections.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:27Streams and reactive programming
- 2:54Profiling tools
- 6:22Promises versus functional effects
- 7:45Start profiling and benchmarking
- 10:34Amb operator in Clojure
- 11:58Mechanical sympathy and SIMD
- 15:30Missionary vs core.async
- 17:16MiniKanren and streams
- 19:23Missionary production use
- 21:50Missionary goals and apps
- 23:35Closing
related talks
23mPractical Clojure Profiling in Production
34mPredictably Fast Clojure
49mA whirlwind tour of functional programming in Clojure
01h 23mKeynote
34mClojure by neophyte
41mParallel Programming, Fork Join, and Reducers
38mProduction Ready ClojureScript: Tales from the Frontier
15mLive Programming a Live Programming Environment: An Experience Report