flushQ is a query on the cache (in-memory) database. I failed to include it, but edited the initial post to fix my mistake.

The application is a server that sits between a data producer and a data consumer. The producer is generating data at 60-100Hz (basically at a monitor's refresh rate) and sending it to the server to be permanently stored. At the same time, the consumer wants to see what is going on with an absolute minimum latency (ideally less than 10 frames). If I were to batch the inserts (say committing once a second), then the consumer won't have access to the most recent data (in this case, there will be a 1 second delay).

(In case you're really curious, this is an application used for data collection in a research lab. If you really want to know more, PM me.)