Page Comparison

...

• Some lists can’t be created at all, and even if they are, there's a high chance they’ll fail when trying to refresh.
• Memory utilization increasing for mod-fgm-manager up to 80% during lists refresh then goes down in few minutes - OOM issue for mod-fqm-manager

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODFQMMGR-501

  but only for creating new lists while the test query is running.
• For mod-lists, CPU utilization was up to 237% for the test with 10 concurrent users and R/W split enabled. Average CPU usage did not exceed 14 % for all other modules.
• Approximately DB CPU usage is up to 98.5%.

...

• 10 m6g.2xlarge EC2 instances located in US East (N. Virginia)us-east-1 

• 1 instance of 2 instances of db.r6g.8xlargexlarge database, writer instance, and reader instance.

• MSK - fse-tenant
  4 kafka.m7g.xlarge brokers in 2 zones

  • Apache Kafka version 3.7.x

  • EBS storage volume per broker 300 GiB

  • auto.create.topics.enable=true

  • log.retention.minutes=480

  • default.replication.factor=3

• OpenSearch ptf-testcluster

  • OpenSearch version 2.13

  • Data nodes

    • Availability Zone(s) - 2-AZ without standby

    • Instance type - r6g.2xlarge.search

    • Number of nodes - 4

    • EBS volume size (GiB) - 300

    • Provisioned IOPS - 3000IOPS

    • Provisioned Throughput (MiB/s) - 250 MiB/s

...