3 ms·
> Regarding native storage, the insert rate really goes down as your table gets large, e.g., Timescale gets 20x higher throughput than PG: https://blog.timescal
by riku_iki 9y ago
> Regarding native storage, the insert rate really goes down as your table gets large, e.g., Timescale gets 20x higher throughput than PG: https://blog.timescale.com/timescaledb-vs-6a696248104e https://blog.timescale.com/timescaledb-vs-6a696248104e
I actually looked at this benchmark briefly, but couldn't find what kind of PostgreSQL schema you used there.
Did you use similar array based schema as was described by Tgress author in his post? https://grisha.org/blog/2015/09/23/storing-time-series-in-postgresql-efficiently/ https://grisha.org/blog/2015/09/23/storing-time-series-in-po...
- RobAtticus 9y agoWe used a pretty basic approach for both: 12 columns - timestamp, hostname, 10 CPU metrics.