pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
How we made Postgres upserts 2-3* quicker than MongoDB
4+ messages / 3 participants
[nested] [flat]

* How we made Postgres upserts 2-3* quicker than MongoDB
@ 2016-01-08 16:37  Mark Zealey <mark@allaroundtheworld.fr>
  0 siblings, 1 reply; 4+ messages in thread

From: Mark Zealey @ 2016-01-08 16:37 UTC (permalink / raw)
  To: pgsql-performance

Hi all, I just wrote an article about the postgres performance 
optimizations I've been working on recently especially compared to our 
old MongoDB platform

https://mark.zealey.org/2016/01/08/how-we-tweaked-postgres-upsert-performance-to-be-2-3-faster-than-...


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: How we made Postgres upserts 2-3* quicker than MongoDB
@ 2016-01-08 17:07  Nicolas Paris <niparisco@gmail.com>
  parent: Mark Zealey <mark@allaroundtheworld.fr>
  0 siblings, 2 replies; 4+ messages in thread

From: Nicolas Paris @ 2016-01-08 17:07 UTC (permalink / raw)
  To: Mark Zealey <mark@allaroundtheworld.fr>; +Cc: pgsql-performance

Hello Mark,

As far as I know, MongoDB is able to get better writing performances
thanks to scaling (easy to manage sharding). Postgresql cannot (is not
designed for - complicated).
Why comparing postgresql & mongoDB performances on a standalone
instance since mongoDB is not really designed for that ?

Thanks for the answer and for sharing,


2016-01-08 17:37 GMT+01:00 Mark Zealey <mark@allaroundtheworld.fr>:
> Hi all, I just wrote an article about the postgres performance optimizations
> I've been working on recently especially compared to our old MongoDB
> platform
>
> https://mark.zealey.org/2016/01/08/how-we-tweaked-postgres-upsert-performance-to-be-2-3-faster-than-...
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: How we made Postgres upserts 2-3* quicker than MongoDB
@ 2016-01-08 17:16  Mark Zealey <mark@allaroundtheworld.fr>
  parent: Nicolas Paris <niparisco@gmail.com>
  1 sibling, 0 replies; 4+ messages in thread

From: Mark Zealey @ 2016-01-08 17:16 UTC (permalink / raw)
  To: Nicolas Paris <niparisco@gmail.com>; +Cc: pgsql-performance

On 08/01/16 19:07, Nicolas Paris wrote:
> Hello Mark,
>
> As far as I know, MongoDB is able to get better writing performances
> thanks to scaling (easy to manage sharding). Postgresql cannot (is not
> designed for - complicated).
> Why comparing postgresql & mongoDB performances on a standalone
> instance since mongoDB is not really designed for that ?

Yes you can get better performance with mongo via the sharding route but 
there are a number of quite bad downsides to mongo sharding - limited 
ability to perform aggregation, loss of unique key constraints other 
than the shard key, requires at minimum 4-6* the hardware (2 replicas 
for each block = 4 + 2 * mongos gateway servers)... Actually pretty 
similar to the issues you see when trying to scale a RDBMS via 
sharding... We tried doing some mongo sharding and the result was a 
massive drop in write performance so we gave up pretty quickly...

Mark


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: How we made Postgres upserts 2-3* quicker than MongoDB
@ 2016-01-08 17:43  Scott Marlowe <scott.marlowe@gmail.com>
  parent: Nicolas Paris <niparisco@gmail.com>
  1 sibling, 0 replies; 4+ messages in thread

From: Scott Marlowe @ 2016-01-08 17:43 UTC (permalink / raw)
  To: Nicolas Paris <niparisco@gmail.com>; +Cc: Mark Zealey <mark@allaroundtheworld.fr>; pgsql-performance

On Fri, Jan 8, 2016 at 10:07 AM, Nicolas Paris <niparisco@gmail.com> wrote:
>
> 2016-01-08 17:37 GMT+01:00 Mark Zealey <mark@allaroundtheworld.fr>:
>> Hi all, I just wrote an article about the postgres performance optimizations
>> I've been working on recently especially compared to our old MongoDB
>> platform
>>
>> https://mark.zealey.org/2016/01/08/how-we-tweaked-postgres-upsert-performance-to-be-2-3-faster-than-...

> Hello Mark,
>
> As far as I know, MongoDB is able to get better writing performances
> thanks to scaling (easy to manage sharding). Postgresql cannot (is not
> designed for - complicated).
> Why comparing postgresql & mongoDB performances on a standalone
> instance since mongoDB is not really designed for that ?
>
> Thanks for the answer and for sharing,

I think the part where he mentioned that it's a lot easy to do roll up
and reporting queries etc. on a sql database justified the comparison
between the two in general. At which point PostgreSQL would normally
be considered the underdog in write performance, at least in the past.
So comparing the two makes perfect sense.


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2016-01-08 17:43 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-01-08 16:37 How we made Postgres upserts 2-3* quicker than MongoDB Mark Zealey <mark@allaroundtheworld.fr>
2016-01-08 17:07 ` Nicolas Paris <niparisco@gmail.com>
2016-01-08 17:16   ` Mark Zealey <mark@allaroundtheworld.fr>
2016-01-08 17:43   ` Scott Marlowe <scott.marlowe@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox