Title
#users-market-data
f

Franco Almonacid

11/10/2022, 2:36 PM
Hello everyone, we are having troubles while inserting data on QuestDB. A bit of context: we are inserting live crypto market-data into several tables at the same time, each table has it's own process writing data into it. Everything runs ok until there is a peak in the amount of data. Looking at the DB server there are lots of QuestDB Java processes in
D status
. A peak looks something like this:
Table 1: 6000 rows per second 
Table 2: 2000 rows per second
Table 3: 3000 rows per second
Table 4: 1000 rows per second
Table config:
maxUncommittedRows = 100000
commitLag = 4s
GCP Instance:
8 CPU
32GB RAM
SSD
Are we missing any config? or do you guys have any tip for tuning QuestDB?