Five Easy to Miss PostgreSQL Query Performance Bottlenecks

• postgrest

  103 22,550 9.8 Haskell

  REST API for any Postgres database

  

For OLAP-style use-cases, I wouldn't recommend SQLite, but rather something equally (apparently) unfashionable: stored procedures.

In both cases, the goal is to save the time spent round-tripping queries and responses to the DB. But with OLAP, you more-than-likely have a large dataset that needs its own dedicated beefy DB to process. So rather than moving the data to the code (with e.g. SQLite), move the code to the data (by moving as much of your business layer as possible into the DB. Or possibly all of it, ala https://postgrest.org/.)

• factory_boy

  3 3,434 6.6 Python

  A test fixtures replacement for Python

  

When releasing a new application (or feature) I've always loaded each table in my development environments database with a few million rows. Tools like Python's Factory Boy [1] or Ruby's Factory Bot [2] make this trivial.

After the data is loaded up, start navigating through the application and it will become evident where improvements need to be made. Tools like Django Debug Toolbar [3] help expose where the bad ORM calls are or also by tailing Postgres log files.

[1] https://github.com/FactoryBoy/factory_boy

• Scout Monitoring

  www.scoutapm.com featured

  Free Django app performance insights with Scout Monitoring. Get Scout setup in minutes, and let us sweat the small stuff. A couple lines in settings.py is all you need to start monitoring your apps. Sign up for our free tier today.

  

• factory_bot

  30 7,889 7.8 Ruby

  A library for setting up Ruby objects as test data.

  

[2] https://github.com/thoughtbot/factory_bot

• django-debug-toolbar

  21 7,938 8.3 Python

  A configurable set of panels that display various debug information about the current request/response.

  

Suggest a related project