Re: A Timeseries Case Study: InfluxDB VS PostgreSQL
Hi All, Full disclosure: I'm a Timescale employee. Fabio, really interesting analysis and we can generally confirm the conclusions of your tests. As Thomas pointed out above, TimescaleDB is an open-source time-series database packaged as Postgres extension. We are always interested in performance comparisons between TimescaleDB and vanilla Postgres and have run a few ourselves (compared to 9.6 and insert rates/ease-of-use in PG10). We'll of course be looking at comparisons to PG11 and where improvements in PG11 also carry over to TimescaleDB. Third-party comparisons are also welcome, especially from someone well-acquainted with Postgres. We have also run benchmarks comparing TimescaleDB and MongoDB that might be useful/interesting for folks here: https://blog.timescale.com/how-to-store-time-series-data-mongodb-vs-timescaledb-postgresql-a73939734016 And in reference to the earlier discussion of InfluxDB, here's a similar post comparing TimescaleDB with InfluxDB: https://blog.timescale.com/timescaledb-vs-influxdb-for-time-series-data-timescale-influx-sql-nosql-36489299877 Finally, if you're interested, here's the open source tool we use to run our database comparison benchmarks: https://github.com/timescale/tsbs Let me know if you have any TimescaleDB specific questions! On Fri, Sep 7, 2018 4:08 AM, Benjamin Scherrey scher...@proteus-tech.com wrote: Interesting and useful article, Fabio. I'm actually quite curious about your evaluation of MongoDB & Postgres. I've been operating under the opinion that MongoDB has been obsoleted in every respect by Postgres and am curious as to whether there are any credible use cases where, given the opportunity to choose from the beginning which technology to build a new product on, I would ever select MongoDB over Postgres given the choice between them. best regards, - - Ben Scherrey On Fri, Sep 7, 2018, 5:16 PM Fabio Pardi wrote: Hi Achilleas, I'm glad you like the article. Probably I will find the time to come back to the topic when I'm done comparing Mongodb with PostgreSQL regards, fabio pardi On 07/09/18 11:18, Achilleas Mantzios wrote: > Nice read! Wonder if you could repeat the tests on pgsql 10.5 and btree/BRIN. TimescaleDB | Head of Marketing & Communityc: 908.581.9509 335 Madison Ave.New York, NY 10017http://www.timescale.com/ https://github.com/timescale/timescaledb
Re: How Many Partitions are Good Performing
This is the blog post that Rakesh referenced: https://blog.timescale.com/time-series-data-postgresql-10-vs-timescaledb-816ee808bac5 Please note, this analysis is done in the context of working with time-series data, where 1000s of chunks is not uncommon because of the append-mostly nature of the workload. On Mon, Jan 8, 2018 at 6:54 PM, Rakesh Kumar wrote: > > You should have read carefully what I wrote. 1000 is not an upper > limit. 1000 partition is the number after which performance starts > dropping . > > There is a blog in www.timescale.com which also highlights the same. > > Sent: Monday, January 08, 2018 at 6:20 PM > From: "Kumar, Virendra" > To: "pgsql-gene...@postgresql.org" > Subject: How Many Partitions are Good Performing > > Can somebody tell us how many partitions are good number without impacting > the performance. We are hearing around a thousand, is that a limit. Do we > have plan to increase the number of partitions for a table. We would > appreciate if somebody can help us with this? > > Regards, > Virendra > > > > This message is intended only for the use of the addressee and may contain > information that is PRIVILEGED AND CONFIDENTIAL. > > If you are not the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, please erase all copies of the > message > and its attachments and notify the sender immediately. Thank you. > > -- TimescaleDB* | *Growth & Developer Evangelism c: 908.581.9509 335 Madison Ave. New York, NY 10017 http://www.timescale.com/ https://github.com/timescale/timescaledb
Re: Supartitions in PGSQL 10
Virenda, is this time-series data you're working with? On Mon, Jan 8, 2018 at 4:12 PM, Kumar, Virendra wrote: > Team, > > > > Can you please let us know if Sub-partitions are supported in PGSQL > (declarative partitions) 10.1. If yes can it be list-list partitions. We > have a situation where a table is very big having around 2 billion rows and > is growing. We want to use partitions but not sure if sub-partitions are > available. The partition key we are looking for is having around 8000 > different values so it will be 8000 partitions and I think that number is > really too big number of partitions. For your information RDBMS is not yet > Postgres, we are evaluating it to see if it can support. Please suggest. > > > > Regards, > > Virendra > > -- > > This message is intended only for the use of the addressee and may contain > information that is PRIVILEGED AND CONFIDENTIAL. > > If you are not the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, please erase all copies of the > message > and its attachments and notify the sender immediately. Thank you. > -- TimescaleDB* | *Growth & Developer Evangelism c: 908.581.9509 335 Madison Ave. New York, NY 10017 http://www.timescale.com/ https://github.com/timescale/timescaledb
