Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
TimescaleDB
An open-source time-series SQL database optimized for fast ingest and complex queries. Packaged as a PostgreSQL extension.
Whenever I see these posts from TimescaleDB, I always want to ask them how it compares in performance to alternative extensions that implement the same features, rather than just comparing TimescaleDB to vanilla PostgreSQL.
For example, they mention their automated data retention and how it's achieved with one SQL command, and how DELETEing records is a very costly operation, and how "even if you were using Postgres declarative partitioning you’d still need to automate the process yourself, wasting precious developer time, adding additional requirements, and implementing bespoke code that needs to be supported moving forward".
There's zero mention anywhere of pg_partman, which does all of these things for you equally as simply, and is a fully OSS free alternative [0].
I get that it's a PG extension that competes with their product. I know that TimescaleDB does a few other things that pg_partman does not. But I can't help but find its (seemingly) purposeful omission in these, otherwise very thorough blog posts, misleading.
[0] https://github.com/pgpartman/pg_partman/blob/master/doc/pg_p...
Seconded. I understand that Timescale extends Postgres, but I'd still like to see performance comparisons relative to other time-series databases such as InfluxDB.
Shameless self-plug: we're also building database technology for embedding vectors (https://milvus.io) - when doing query performance comparisons, we get several orders of magnitude of performance improvement over traditional databases. It's an unfair comparison, so we generally avoid it.
This is a reasonable benchmark from the Clickhouse folks for single table query performance over smallish data sets (10s of GB of data). Most of the DW vendors are on there.
https://benchmark.clickhouse.com/
Timescale apparently lags pretty far behind modern columnstore engines.
Related posts
- Opinions and Suggestions for PostgreSQL Extension under Development
- I would like to know your advice, I am creating an inventory control software, and I would like to use the PostgreSQL database instead of SQL Server, Could you give me your opinions of the advantages and disadvantages of using one or the other, Thank you.
- How we made data aggregation on PostgreSQL better and faster
- Ingesting an S3 file into an RDS PostgreSQL table
- I'm building a real-time monitoring system for metrics of servers in Rust !