DuckLake Speed
This mostly a general question to see if my issue is simple (and on my end).
I got DuckLake working for simple table creation and insert scripts. I can view the table and records inserted.
But, it’s very slow to take any action (like, 10-15 seconds to do any kind of write action and 5-10 seconds for a read action - with one table and less than 50 records - and only writing one or two records at a time). I understand the difference between a standard transactional database and this, but still seems slower than I’d expect.
I’m using CE, using docker-compose, hosting all containers on a VM on Hetzner with 8gb of ram, and using Hetzners s3 compatible object storage.
I know that 8gb isn’t much for numerous containers all working together, but with all other actions the performance is perfectly acceptable.
So, is it possible the server specs are the issue? Something different with Hetzners object storage? Misconfiguration? Possible I just don’t understand how DuckLake is expected to work?
Thanks for your help!
I got DuckLake working for simple table creation and insert scripts. I can view the table and records inserted.
But, it’s very slow to take any action (like, 10-15 seconds to do any kind of write action and 5-10 seconds for a read action - with one table and less than 50 records - and only writing one or two records at a time). I understand the difference between a standard transactional database and this, but still seems slower than I’d expect.
I’m using CE, using docker-compose, hosting all containers on a VM on Hetzner with 8gb of ram, and using Hetzners s3 compatible object storage.
I know that 8gb isn’t much for numerous containers all working together, but with all other actions the performance is perfectly acceptable.
So, is it possible the server specs are the issue? Something different with Hetzners object storage? Misconfiguration? Possible I just don’t understand how DuckLake is expected to work?
Thanks for your help!
