Optimizing PostgreSQL for GeoQlik
PostgreSQL is a fantastic resource and provides an ideal environment for hosting your geospatial data. However, out of the box the performance can leave a bit to be desired. Luckily, with a few tweaks we can greatly improve the performance of GeoQlik deployments.
Below, we’ve listed a few of the configuration modifications we make for nearly every installation we do. These settings can be modified from the postgresql.conf file or, for even easier access, use the Backend Configuration Editor. As we all know, every installation and deployment is different so you may have to adjust some of these settings depending on your environment and hardware however this provides a solid baseline. Here our most common changes:
work_mem – The default value here is generally 1MB. We generally allocate at least 16MB.
maintenance_work_mem – Default value of 16MB, we increase it to 32MB.
checkpoint_segments – Default value of 3. We recommend upping this to 6.
random_page_cost – Default value of 4.0. Modify this to 2.0.
wal_buffers – Default value of 64kB. We bump this up to at least 1MB.
shared_buffers – Default value typically 32MB. Recommend 500MB.
Whether you are just begining your geospatial analytics journey, or you are trying to tune a complex environment, contact Aculytics today to discuss how we can help you succeed.