Talk:PowerDNS OpenDBX Backend/Comparison

Which settings are necessary to get a better PostgreSQL performance?

1) On a 256MB machine, you might want to:

   echo 96000000 > /proc/sys/kernel/shmmax; echo 96000000 > /proc/sys/kernel/shmall
   Set shared_buffers = 4000 in postgresql.conf and restart.

2) Make sure you've run an ANALYZE in your database after loading the test data. The PostgreSQL query planner assumes tables are empty until analyze tells it different. If you've deleted and reloaded the data, run a VACUUM FULL ANALYZE in the database before running the benchmark.

3) Try setting enable_seqscan=false in postgresql.conf. On small data sets, PostgreSQL will frequently avoid using indexes. In a benchmark like this, where all the data will end up cached, that could slow it down a fair bit, even though for a general purpose database with more concurrency it might make sense.