~/talk

Big Data in Memory

Talkat SpringOne2GX 2014 · 2014-09-08..09-11· [web-performance]
slides:none on file

Claims a binary, model-driven encoding cuts memory and CPU drastically while keeping the same Spring APIs and workflow. Uses Spring Integration, Reactor, GemFire and Java NIO to replace fat Java objects with generated binary codecs; demo shows 7.4kB XML → 25kB Java → 450 bytes per record and running 10 million derivative contracts in memory on a laptop. Benchmarks: 5M trades: standard Java serialization 200s vs binary nio 2s, much smaller heap, far fewer GC pauses, and RTI Telco pipeline handling ~100k/s average (peaks near 800k–10M/s).

AI-written summary · about

  1. 0:00Introduction to big data
  2. 1:53Memory efficiency in Java
  3. 9:36Demo setup and trade data
  4. 22:18Serialization performance tests
  5. 30:04Binary data advantages
  6. 41:21Real-time processing at scale
  7. 53:21Telco network analytics
  8. 1:00:03Optimization strategies
  9. 1:05:19Q&A session
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.