https://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/Recent changes to Performance TuningenThu, 05 Apr 2012 17:01:13 -0000https://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v19 +++ v20 @@ -23,3 +23,5 @@ ***Follow us on twitter*** to receive new feature notifications: http://www.twitter.com/opencdrrate/ + +***Join our LinkedIn group*** to open discussions on features you would like to see in the system. http://www.linkedin.com/groups/OpenCDRRate-4381972 </pre>DTHThu, 05 Apr 2012 17:01:13 -0000https://sourceforge.netff5b1b897c0ffb9d338b853e8584deb28d2f6412https://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v18 +++ v19 @@ -20,3 +20,6 @@ ***Indices*** - A large part of database tuning is in the indexes themselves. We have created indices for the most common queries we feel will be executed on the database but individual installations will still require site-specific tuning. The need for this type of tuning will increase as your call volume increases. ***Delete Expired Rate Sheets*** - Deleting rate sheets/decks that have expired will improve performance as there will be fewer records to process during rating. + + +***Follow us on twitter*** to receive new feature notifications: http://www.twitter.com/opencdrrate/ </pre>DTHThu, 29 Mar 2012 17:34:35 -0000https://sourceforge.net4477250ea1338dc50c471f97740317acb7d31d26https://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v17 +++ v18 @@ -17,4 +17,6 @@ ***log_min_duration_statement*** - This feature in Postgres will log each query/command and its run-time. This can be very useful to identify slow-running queries. Logging "all" commands can be too much load on the server. We recommend logging only commands that take longer than 10 seconds to run. The information collected can be used to determine if indices need to be created or if additional maintenance is required. +***Indices*** - A large part of database tuning is in the indexes themselves. We have created indices for the most common queries we feel will be executed on the database but individual installations will still require site-specific tuning. The need for this type of tuning will increase as your call volume increases. + ***Delete Expired Rate Sheets*** - Deleting rate sheets/decks that have expired will improve performance as there will be fewer records to process during rating. </pre>DTHThu, 22 Sep 2011 15:31:47 -0000https://sourceforge.net34f60d6925996a80deb5d81971a0135e3bcf1d90https://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v16 +++ v17 @@ -1,5 +1,7 @@ ***This is a first-release of the documentation. Additional detail will be added as the project matures.*** +These are RECOMMENDATIONS ONLY based on our own internal testing. Do not blindly implement these recommendations without performing your own testing first. + ***Vacuum*** - We recommend performing a VACUUM daily during idle hours as well as an infrequent VACUUM FULL. ***Analyze*** - We recommend performing an ANALYZE on a daily basis. This can be done in conjunction with the daily VACUUM. </pre>DTHFri, 16 Sep 2011 00:23:13 -0000https://sourceforge.net9b13f284b84dd48d579c945ca053fe5b578e40b6https://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v15 +++ v16 @@ -15,4 +15,4 @@ ***log_min_duration_statement*** - This feature in Postgres will log each query/command and its run-time. This can be very useful to identify slow-running queries. Logging "all" commands can be too much load on the server. We recommend logging only commands that take longer than 10 seconds to run. The information collected can be used to determine if indices need to be created or if additional maintenance is required. -***Delete Expired Rate Sheets*** - Deleting rate sheets/decks that have expired will improve performance as there will be fewer records to process. +***Delete Expired Rate Sheets*** - Deleting rate sheets/decks that have expired will improve performance as there will be fewer records to process during rating. </pre>DTHMon, 05 Sep 2011 15:55:25 -0000https://sourceforge.netd7f0dcee9517111c9032d55dee90eca0fad231a7https://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v14 +++ v15 @@ -6,7 +6,7 @@ ***Reindex*** - A periodic REINDEX may be required to remove index bloat. -***shared_buffers*** - The default shared_buffers setting in Postgres is low. If your server will be doing primarily database work, you can up to shared_buffers to be between 20% - 25% of the total system memory. You may need to play with this setting to see what works best for you. +***shared_buffers*** - The default shared_buffers setting in Postgres is low. If your server will be doing primarily database work, you can up the shared_buffers to be between 20% - 25% of the total system memory. You may need to play with this setting to see what works best for you. ***wal_buffers*** - The default write-ahead log setting in Postgres is low. We recommending increasing it to 8MB. </pre>DTHMon, 05 Sep 2011 15:54:40 -0000https://sourceforge.net45aa4a86153ad4aa47cfc7574ce134cf5763e93dhttps://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v13 +++ v14 @@ -10,6 +10,7 @@ ***wal_buffers*** - The default write-ahead log setting in Postgres is low. We recommending increasing it to 8MB. +***effective_cache_size*** - This can be set to 50% - 75% of your available system memory. ***log_min_duration_statement*** - This feature in Postgres will log each query/command and its run-time. This can be very useful to identify slow-running queries. Logging "all" commands can be too much load on the server. We recommend logging only commands that take longer than 10 seconds to run. The information collected can be used to determine if indices need to be created or if additional maintenance is required. </pre>DTHMon, 05 Sep 2011 15:48:55 -0000https://sourceforge.net3415b253e117cd22ce4e9bec69499207b0cd156chttps://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v12 +++ v13 @@ -8,6 +8,10 @@ ***shared_buffers*** - The default shared_buffers setting in Postgres is low. If your server will be doing primarily database work, you can up to shared_buffers to be between 20% - 25% of the total system memory. You may need to play with this setting to see what works best for you. +***wal_buffers*** - The default write-ahead log setting in Postgres is low. We recommending increasing it to 8MB. + + + ***log_min_duration_statement*** - This feature in Postgres will log each query/command and its run-time. This can be very useful to identify slow-running queries. Logging "all" commands can be too much load on the server. We recommend logging only commands that take longer than 10 seconds to run. The information collected can be used to determine if indices need to be created or if additional maintenance is required. ***Delete Expired Rate Sheets*** - Deleting rate sheets/decks that have expired will improve performance as there will be fewer records to process. </pre>DTHMon, 05 Sep 2011 15:46:52 -0000https://sourceforge.netc47cc9c5a0e33332a7d3b1d1fde0ee48008acdf5https://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v11 +++ v12 @@ -6,7 +6,7 @@ ***Reindex*** - A periodic REINDEX may be required to remove index bloat. -***shared_buffers*** - The default shared_buffers setting in Postgres is low. If your server will be doing primarily database work, you can up to shared_buffers to be between 10% - 15% of the total system memory. You may need to play with this setting to see what works best for you. +***shared_buffers*** - The default shared_buffers setting in Postgres is low. If your server will be doing primarily database work, you can up to shared_buffers to be between 20% - 25% of the total system memory. You may need to play with this setting to see what works best for you. ***log_min_duration_statement*** - This feature in Postgres will log each query/command and its run-time. This can be very useful to identify slow-running queries. Logging "all" commands can be too much load on the server. We recommend logging only commands that take longer than 10 seconds to run. The information collected can be used to determine if indices need to be created or if additional maintenance is required. </pre>DTHSun, 04 Sep 2011 22:49:14 -0000https://sourceforge.netdef8fd1f1d6b8f3cb937a801edcc0cbcc2af6b08https://sourceforge.net/p/opencdrrate/home/Performance%2520Tuning/<pre>--- v10 +++ v11 @@ -6,6 +6,8 @@ ***Reindex*** - A periodic REINDEX may be required to remove index bloat. +***shared_buffers*** - The default shared_buffers setting in Postgres is low. If your server will be doing primarily database work, you can up to shared_buffers to be between 10% - 15% of the total system memory. You may need to play with this setting to see what works best for you. + ***log_min_duration_statement*** - This feature in Postgres will log each query/command and its run-time. This can be very useful to identify slow-running queries. Logging "all" commands can be too much load on the server. We recommend logging only commands that take longer than 10 seconds to run. The information collected can be used to determine if indices need to be created or if additional maintenance is required. ***Delete Expired Rate Sheets*** - Deleting rate sheets/decks that have expired will improve performance as there will be fewer records to process. </pre>DTHSun, 04 Sep 2011 20:58:34 -0000https://sourceforge.net2f29639670381dc59d190d6ebecc7955896cecee