commit | a8a47e06d84f696656479bf507e802a422effd5a | [log] [tgz] |
---|---|---|
author | Prakhar Pandey <prakhar.pandey@bell.ca> | Thu Apr 14 12:15:00 2022 -0400 |
committer | Lukasz Rajewski <lukasz.rajewski@orange.com> | Fri Apr 22 07:08:06 2022 +0000 |
tree | 7481b5fe44d444354cb771122e13bbf0e331d927 | |
parent | 2205e0c6bbc9ed05b0fe4a1af88532d95652881f [diff] |
[POLICY] Increase hikari connection pool size for PAP & API We saw some bottlenecks during S3P testing of API component due to the default connection pool size of 10. Setting it to 20 based on the number of parallel threads used for performance tests. The change is required because prior to spring boot migration (Istanbul and earlier), the default connection size was 32 so it was never a problem for running load tests. Issue-ID: POLICY-4007 Change-Id: Iaaa573d5fce0298e3aff05a27c2e845840a6cb06 Signed-off-by: Prakhar Pandey <prakhar.pandey@bell.ca>
diff --git a/kubernetes/policy/components/policy-api/resources/config/apiParameters.yaml b/kubernetes/policy/components/policy-api/resources/config/apiParameters.yaml index c08b035..e6cf2b3 100644 --- a/kubernetes/policy/components/policy-api/resources/config/apiParameters.yaml +++ b/kubernetes/policy/components/policy-api/resources/config/apiParameters.yaml
@@ -29,6 +29,8 @@ driverClassName: org.mariadb.jdbc.Driver username: "${SQL_USER}" password: "${SQL_PASSWORD}" + hikari: + maximumPoolSize: 20 jpa: properties: hibernate:
diff --git a/kubernetes/policy/components/policy-pap/resources/config/papParameters.yaml b/kubernetes/policy/components/policy-pap/resources/config/papParameters.yaml index 6f501b8..00f7b9b 100644 --- a/kubernetes/policy/components/policy-pap/resources/config/papParameters.yaml +++ b/kubernetes/policy/components/policy-pap/resources/config/papParameters.yaml
@@ -29,6 +29,8 @@ driverClassName: org.mariadb.jdbc.Driver username: "${SQL_USER}" password: "${SQL_PASSWORD}" + hikari: + maximumPoolSize: 20 jpa: properties: hibernate: