To fine-tune the PostgreSQL database server, modify the following memory configuration parameters in the <install_dir>/3rd party/postgresql/data/postgresql.conf file:
shared_buffers: Determines how much memory is dedicated to PostgreSQL for caching data. For better performance, you can set this parameter value to one-fourth of the available RAM.
effective_cache_size: Determines how much memory is available for disk caching by the operating system and within the database. You can estimate the size of this parameter by taking into account what is used by the operating system and other applications. You can allocate half of the total available system memory to this parameter.
work_mem: Determines the amount of memory used by internal sort operations and hash tables before switching to temporary disk files. The value is specified in kilobytes. The default value is 1024 kilobytes (1 MB).
For a complex query, several sort or hash operations might be running in parallel. Each operation uses as much memory as the value specified for work_mem before it starts to put data into temporary disk files. If you are scheduling more reports on your Sentinel Rapid Deployment system, set this value between 500MB and 1GB.
maintenance_work_mem: Determines the maximum amount of memory to be used in maintenance operations of the database, such as VACUUM, CREATE INDEX, and ALTER TABLE ADD FOREIGN KEY. The value is specified in kilobytes. The default value is 16384 kilobytes (16 MB).
Larger settings might improve the performance for vacuuming and for restoring database dumps. Keep this parameter unchanged because, the default value is sufficient for the Sentinel Rapid Deployment operations.