Avoiding End-of-Day Halts with TorQ

Jonny Press data capture, kdb, kdb+, TorQ 3 Comments

kdb+tick is great, but there’s a problem- when the RDB (real time database) writes to disk on its daily schedule, users cannot access that day’s data until the write out is complete.  There are various solutions to this issue including: using something similar to w.q to write out the data periodically intraday have a replicated system and staggering the save down, …

Jonny PressAvoiding End-of-Day Halts with TorQ

Recovering Corrupt Tickerplant Logs

Glen Smith data capture, kdb, kdb+, TorQ 1 Comment

Corrupt tickerplant logs are a curse that no one deserves but that doesn’t stop them from happening even to the best of us. However, all hope is not lost as it is possible to recover the good messages and discard the bad. In this post we will extend upon the standard rescuelog procedure to recover as much as possible from the …

Glen SmithRecovering Corrupt Tickerplant Logs

Supporting A kdb+ System: Online Training

Jonny Press kdb, kdb+, training Leave a Comment

We are pleased to announce that due to popular demand we’ve added new content to our online training course.  The additional material is on supporting a kdb+ system (something we have some experience of).  The new material covers: overview of a real time data capture architecture (kdb+tick) kdb+tick setup health checking, monitoring, support and maintenance of a data capture system on …

Jonny PressSupporting A kdb+ System: Online Training

Supporting kdb+ Tick

AquaQ Admin kdb, kdb+ 4 Comments

Many financial institutions use kdb+ tick to capture and store market data. The same technology stack can be used to capture, store and analyse other forms of real time streaming data including sensor data from manufacturing production lines, usage data from utility smart meters, or telemetry data from Formula 1 cars. At AquaQ we provide onsite and nearshore 24/7 support …

AquaQ AdminSupporting kdb+ Tick

Garbage Collection in kdb+

AquaQ Admin kdb, kdb+ 6 Comments

The aim of this article is give an understanding of how kdb+ uses and releases memory, and the options available to modify the behaviour. kdb+ allocates memory in powers of 2.  A vector of data will always be placed into a memory block which is the next power of two up from the raw data size (and allowing for some …

AquaQ AdminGarbage Collection in kdb+