Re: A Timeseries Case Study: InfluxDB VS PostgreSQL - Mailing list pgsql-general

From Andrew Staller
Subject Re: A Timeseries Case Study: InfluxDB VS PostgreSQL
Date
Msg-id 6b25525b-8c36-620e-5da0-c900a7720c19@mixmax.com
Whole thread Raw
In response to Re: A Timeseries Case Study: InfluxDB VS PostgreSQL  (Benjamin Scherrey <scherrey@proteus-tech.com>)
List pgsql-general
a {word-wrap:normal;word-break:break-word;}.background-contain {background-size:contain;}@media only screen and (max-width:600px) {.container {-webkit-text-size-adjust:none !important;}.container,.palm-one-whole {width:100% !important;min-width:100% !important;}.palm-one-half {width:50% !important;min-width:50% !important;box-sizing:border-box;}blockquote .container,blockquote .container div,blockquote .container table {width:auto !important;min-width:0 !important;position:relative !important;}img {max-width:100%;}.border-outer,.border-middle,.border-inner,.inner,[title="separator"] {width:100% !important;}.innercell {padding:8px !important;}.palm-block {display:block !important;}td.palm-one-whole {display:inline-block !important;padding:0;}td.palm-one-whole:first-child:not(:only-child) {margin-bottom:16px;}td.hostname {padding-top:3px !important;}}@media only screen and (min-width:601px) {.preview-card {max-width:600px !important;}}@media only screen and (min-device-width :320px) and (max-device-width :568px),only screen and (min-device-width :768px) and (max-device-width :1024px),only screen and (max-device-width:640px),only screen and (max-device-width:667px),only screen and (max-width:480px){.container {width:100% !important;min-width:100% !important;}.p,.small,li,font[size="2"],font[size="3"] {font-size:1em !important;}}@media only screen and (min-device-width :320px) and (max-device-width :568px),only screen and (min-device-width :768px) and (max-device-width :1024px),only screen and (min-device-width :1224px) {.message-wrapper {padding-top:6px;}.apple-only[style] {display:block !important;max-height:none !important;line-height:normal !important;overflow:visible !important;height:auto !important;width:100% !important;position:relative !important;}.no-apple {display:none !important;}form {font-size:inherit;}input[type="text"] {height:43px;padding-left:4px !important;}button:hover {cursor:pointer;}}@media only screen and (min-device-width :1224px) {.apple-mail-form {display:block !important;background-color:white !important;}}* [office365] .outlook-com-hidden {display:none !important;}* [office365] .outlook-com-button {display:block;}* [office365] .outlook-com-only {display:block !important;max-height:none !important;line-height:normal !important;overflow:visible !important;height:auto !important;width:100% !important;position:relative !important;}.ExternalClass {width:100%;}.ExternalClass .outlook-com-button {display:block;}.ExternalClass button {height:auto;}.ExternalClass .outlook-com-hidden {display:none !important;}.ExternalClass .outlook-com-only {display:block !important;max-height:none !important;line-height:normal !important;overflow:visible !important;height:auto !important;width:100% !important;position:relative !important;}.ExternalClass .ecxlabels {display:none !important;}.ExternalClass .ecxlabels {display:none !important;}.ExternalClass .ecxarrow {display:none !important;}.ExternalClass cite >div + div {padding:0 0 4px 0;}.ExternalClass .h1 {padding-bottom:5px;}.ExternalClass .h2 {padding-bottom:5px;}.ExternalClass .h3 {padding-bottom:5px;}.ExternalClass [lang="brand-pinterest"] {width:280px !important;}
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 scherrey@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 <f.pardi@portavita.eu> 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 & Community
c: 908.581.9509

335 Madison Ave. 
New York, NY 10017

pgsql-general by date:

Previous
From: amul sul
Date:
Subject: Re: connection error
Next
From: David Steele
Date:
Subject: Re: pgbackrest when data/base is symlinked to another volume