These are chat archives for bluestreak01/questdb

Jun 2015
Vlad Ilyushchenko
Jun 30 2015 19:20
Hey Sirinath, yes, single writer pattern may not be very convenient or simple in multi-channel data acquisition, but it is wait- and lock-free and by far the fastest. I have an example here: that stores data produced by multiple thread in same journal using disruptor multiple-producer-single-consumer setup.
on SQL front, the entire language implementation is going to be stream based, including multi-journal joins and aggregation (more specifically - re-sampling). It is going to provide full ANSI SQL 92 support with extensions for handling time series. Unlike Java8 streams, nfsdb streams are reusable, which will contain memory allocation at bare minimum.