11 ms·

Does this release add any features that would keep you from going for a NoSQL solution? How does it for instance compare to MongoDB in terms of raw performance

Does this release add any features that would keep you from going for a NoSQL solution? How does it for instance compare to MongoDB in terms of raw performance and scalability? (Not mentioning of course the difference in schema-less and relational design)

crad 16y ago
I have found Apples to Apples (fsync off in PgSQL) and doing key/value store in PgSQL, PgSQL performed on par with, or slightly faster than MongoDB, using my admittedly not fully baked KVPBench app - http://github.com/gmr/kvpbench http://github.com/gmr/kvpbench.
- gxti 16y ago
  FUN FACT: (and you probably already know this but many do not): "fsync = off" is postgresql-ese for "please destroy all my data". Don't do it. Ever. The 9.0 docs are finally improving the language here to indicate that you must not set fsync off if you value your job. Setting "synchronous_commit = off" nets you 99.9% of the performance improvement without the possibility of corrupting your entire database.
  - crad 16y ago
    You might enjoy my fsync related photo: http://www.flickr.com/photos/gavinmroy/4638958958/ http://www.flickr.com/photos/gavinmroy/4638958958/ And the presentation it came from: http://www.scribd.com/doc/31669670/PostgreSQL-and-NoSQL http://www.scribd.com/doc/31669670/PostgreSQL-and-NoSQL
    - rdeleonp 16y ago
      Very cool presentation.
- xal 16y ago
  why don't you publish the results of your benchmark?
  - crad 16y ago
    I've been trying to find time to do a more in-depth test with multiple servers and include the scale out part of each system. I plan too soon.
    - catch23 16y ago
      Where was the dba-running-with-scissors photo taken? Also, could we get the performance charts in your slides without the 3d-perspective? It's hard to tell relative performance from the angle.
      - crad 16y ago
        Outside our office in New Hope, PA. I'll do better graphs when I release the higher concurrency stats.

crad 16y ago

I have found Apples to Apples (fsync off in PgSQL) and doing key/value store in PgSQL, PgSQL performed on par with, or slightly faster than MongoDB, using my admittedly not fully baked KVPBench app - http://github.com/gmr/kvpbench http://github.com/gmr/kvpbench.

gxti 16y ago
FUN FACT: (and you probably already know this but many do not): "fsync = off" is postgresql-ese for "please destroy all my data". Don't do it. Ever. The 9.0 docs are finally improving the language here to indicate that you must not set fsync off if you value your job. Setting "synchronous_commit = off" nets you 99.9% of the performance improvement without the possibility of corrupting your entire database.
- crad 16y ago
  You might enjoy my fsync related photo: http://www.flickr.com/photos/gavinmroy/4638958958/ http://www.flickr.com/photos/gavinmroy/4638958958/ And the presentation it came from: http://www.scribd.com/doc/31669670/PostgreSQL-and-NoSQL http://www.scribd.com/doc/31669670/PostgreSQL-and-NoSQL
  - rdeleonp 16y ago
    Very cool presentation.
xal 16y ago
why don't you publish the results of your benchmark?
- crad 16y ago
  I've been trying to find time to do a more in-depth test with multiple servers and include the scale out part of each system. I plan too soon.
  - catch23 16y ago
    Where was the dba-running-with-scissors photo taken? Also, could we get the performance charts in your slides without the 3d-perspective? It's hard to tell relative performance from the angle.
    - crad 16y ago
      Outside our office in New Hope, PA. I'll do better graphs when I release the higher concurrency stats.