Code Review / oom.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 2205e0c) | patch
[POLICY] Increase hikari connection pool size for PAP & API 87/128687/4
authorPrakhar Pandey <prakhar.pandey@bell.ca>
Thu, 14 Apr 2022 16:15:00 +0000 (12:15 -0400)
committerLukasz Rajewski <lukasz.rajewski@orange.com>
Fri, 22 Apr 2022 07:08:06 +0000 (07:08 +0000)
commita8a47e06d84f696656479bf507e802a422effd5a
tree7481b5fe44d444354cb771122e13bbf0e331d927tree | snapshot
parent2205e0c6bbc9ed05b0fe4a1af88532d95652881fcommit | 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>
kubernetes/policy/components/policy-api/resources/config/apiParameters.yaml diff | blob | history
kubernetes/policy/components/policy-pap/resources/config/papParameters.yaml diff | blob | history
Introduces the ONAP Platform OOM (ONAP Operations Manager) to efficiently Deploy, Manage, Operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.) and infrastructure (VMs, Containers).