Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

How do PostgreSQL's Hstore and Redis compare performance-wise? This question was asked here, but I would like to compare with a PostgreSQL configuration without durability guarantee, i.e. with synchronous_commit off or with fsync and full_page_writes off.

PostgreSQL 9.3, concurrency level: read committed.

For the record size, read vs write and number of tuples by operation, it would be interesting to know where Hstore and Redis perform better in each of those cases, and if there is any configuration where Hstore would perform better.

share

migration rejected from stackoverflow.com Jan 7 at 16:53

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as primarily opinion-based by Mark Storey-Smith, Paul White, Michael - sqlbot, ypercube, dezso Jan 7 at 16:53

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
Depends tons on the workload. Read-mostly or write heavy? Lots of updates to individual keys, or mostly whole tuple deletes / inserts? Pg version of interest? Concurrency levels? Usual size of records? ... –  Craig Ringer Jan 6 at 15:02
    
PostgreSQL 9.3, concurrency level: read committed. For the record size, read vs write and number of tuples by operation, it would be interesting to know where Hstore and Redis perform better in each of those cases, and if there is any configuration where Hstore would perform better. –  ehmicky Jan 6 at 15:08
2  
Please edit your question with all the basic information. Don't hide it in comments. –  Erwin Brandstetter Jan 6 at 19:56
    
Sounds like you have some fun workload simulation and benchmarking ahead of you then ;-) . Personally I'd be somewhat surprised if using PostgreSQL exclusively as a non-durable key/value store with hstore outperformed a database that's designed to be a non-durable key/value store. PostgreSQL might get ahead if you're doing complex queries and large set operations, the sort of thing Redis can't really do, but otherwise... –  Craig Ringer Jan 7 at 0:09