3 ms·

What’s the insertion capability on the freeware version? Does it handle event time ordering well for distributed injestion? Appreciate the push. It does look

What’s the insertion capability on the freeware version? Does it handle event time ordering well for distributed injestion? Appreciate the push. It does look interesting. I like the idea of working with array native type construct as the mental model is very close to analyzing time series data for a strategy.

srazzaque 7y ago
Ingest - the free version as I'm sure you're aware is 32bit only. So it is limited in how much data it can address. But the /rate/ of ingest I'd imagine is close to that of the 64bit, with the caveat that you'll hit the ceiling sooner (untested). The system I was working with was ingesting in the order of 10s of millions of rows per day from multiple sources. This was obviously the 64bit version. Also if you do plan on using it for anything beyond tinkering and personal research I'd review the licensing. I'm not too sure what is and isn't allowed. Time ordering - yes. The typical architecture of a production system in KDB will have something called a Tickerplant (TP), a process through which all updates must traverse. This will stamp its own timestamp on all the updates it receives. So for time ordering - you can (1) use the TP timestamps, and/or (2) have your source nodes also provide a timestamp in their own column (eg sourceNodeTimestamp), and then you've got some means of detecting skew across your systems with comparisons to the TP timestamps. You could then order your data by whatever timestamp you want to use in your queries.