| Table of Contents |
|---|
...
- Replacing XMX with MaxRAMPercentage do not affect main KPI's. Comparing DI's durations in tests #1 and #2 deltas do not exceed 4 minutes that is acceptable.
- After changing MaxRAMPercentage from default values to recommended 66% Check-in / Check-out response times increased during data import for CI - 15%, for CO - 7%, and it also affected Data import durations - 8 minutes difference in DI test #6.
- Comparing DI durations between configuration #2 and #3 (with limited MaxRAMPercentage) we see 4 minutes differencethat DI slower in configuration #3. Previously known issue with mod-inventory (container stop because of CPU growing) appear much faster in configuration #3 with limited MaxRAMPercentage.
- CPU utilization top three modules:
| Service | Configuration #1 | Configuration #2 | Configuration #3 |
| mod-inventory-b | 254.27 | 305.56 | 216.98 |
| mod-quick-marc-b | 120.83 | 58.49 | 87.44 |
| nginx-okapi | 91.73 | 56.1 | 95.49 |
- Memory consumption top three modules:
| Service | Configuration #1 | Configuration #2 | Configuration #3 |
| mod-inventory-b | 99.4 | 105.84 | 102.32 |
| mod-search-b | 96.43 | 89.1 | 96.81 |
| mod-users-b | 63.08 | 61.58 | 60.63 |
- RDS CPU utilization was close to 96% during CI/CO + Data import
- RDS DB Connections were close to 600 during CI/CO + Data import
...
Infrastructure
PTF -environment pcp1
- 10 m6i.2xlarge EC2 instances located in US East (N. Virginia)us-east-1
1 database instance, writer
Name Memory GIB vCPUs max_connections db.r6g.xlarge
32 GiB 4 vCPUs 2731 - MSK tenant
- 4 m5.2xlarge brokers in 2 zones
Apache Kafka version 2.8.0
EBS storage volume per broker 300 GiB
- auto.create.topics.enable=true
- log.retention.minutes=480
- default.replication.factor=3
...