timescaledb and disk space
Based on the numbers you provided, you should have more than 4 million positions every hour. So it's about 700 bytes per position. It's on a higher side, but doesn't seem unreasonable, depending on the number of position attributes you have.
Thank you.
What about activating compression? is it something that could help optimizing storage, and won't affect traccar performance?
It might help if you have a lot of repeated data, but I don't think it makes sense in a general case.
What recommended compression policy for tc_positions table?
Do not enable compression policy. It will result in issues.
Hello,
recently I switched to latest traccar server and timescaledb, configured retention policy and everything working as expected.
I've about 12k devices sending at 10s interval. I've noticed that disk space used is about 3GB every 1 hour.
is this normal or I'm missing something?
Should I activate compression for timescaledb? https://www.tigerdata.com/docs/use-timescale/latest/compression/about-compression
Regards,