Difference between revisions of "SUNScholar/Optimisations/Database"
Jump to navigation
Jump to search
m |
m |
||
| Line 2: | Line 2: | ||
'''[[SUNScholar/Optimisations|Back to Optimisations]]''' | '''[[SUNScholar/Optimisations|Back to Optimisations]]''' | ||
</center> | </center> | ||
| + | ==Introduction== | ||
| + | As our repository became more popular we noticed that the number database connections increased alarmingly. It is normal web application programming practice to release/sever database connections after a particular programming task on the database is done. | ||
*Increase connection pool parameters | *Increase connection pool parameters | ||
Revision as of 14:08, 26 June 2015
Back to Optimisations
Introduction
As our repository became more popular we noticed that the number database connections increased alarmingly. It is normal web application programming practice to release/sever database connections after a particular programming task on the database is done.
- Increase connection pool parameters
The following db connection parameters are used:
max_connections = 200 max_idle_connections = 400
These paremeters are set in the "build.properties" and "postgresql.conf" files.
Check the relevant wiki guide sections for more details.
- Fix "browse index" configuration to reduce the PostgreSQL database server query load.
http://wiki.lib.sun.ac.za/index.php/SUNScholar/Browse_Indexes
- Vacumn the database regularly
http://wiki.lib.sun.ac.za/index.php/SUNScholar/Daily_Admin
