Juan Hernandez has posted comments on this change. Change subject: core: Set min connection pool size to 1 ......................................................................
Patch Set 1: I guess that we could do some type of calculation according to the available memory. If we assume that each PostgreSQL process consumes approx 26 MiB of RAM (this was the case in the machine where the failure was detected, may be different in other scenarios) and we assume that the engine takes a max of 2 GiB of RAM (the heap is limited by default to 1 GiB, and it usually requires much less, approx 400 MiB in the machine where the failure was detected) then we can calculate the number of connections as follows: max = (ram - 2 GiB) / 26 MiB For a machine with 4 GiB this would result in approx 78 connections. However this is assuming that there are no other things running in the machine, which isn't usually true. That calculation could be performed by the setup application. However, this calculated max should go in the ENGINE_DB_MAX_CONNECTIONS parameter, not in ENGINE_DB_MIN_CONNECTIONS. The min should be probably a fraction of the max, say 50%, or just 1 as increasing it is just a theoretical performance improvement. -- To view, visit http://gerrit.ovirt.org/21188 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I9de2c9e6999cb22a4be99eabb66a7216e673d0d2 Gerrit-PatchSet: 1 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Juan Hernandez <[email protected]> Gerrit-Reviewer: Juan Hernandez <[email protected]> Gerrit-Reviewer: Liran Zelkha <[email protected]> Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No _______________________________________________ Engine-patches mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-patches
