Skip to content

[Performance] big5.cardinality-agg-high regressed in OS 3.1 #18385

@asimmahmood1

Description

@asimmahmood1

Describe the bug

In OS 3 a new execution_hint was added to force using ordinals, which reduced p90 ST from 2402ms to 1905 with hint. With OS 3 concurrent search enabled by default, it dropped to 786ms.

In the nightly bechmark we can see similar numbers:

Big5 Term Aggregation Queries
2.19.1 3.0.0 3.1.0
May 26, 2025 May 27, 2025 May 26, 2025 May 27, 2025 May 26, 2025 May 27, 2025
Rows p90_value p90_value p90_value p90_value p90_value p90_value
cardinality-agg-high 2,285 2,315 648 630 874 889

https://us-east-1.quicksight.aws.amazon.com/sn/account/amazonbi/dashboards/fc187b76-79eb-4184-bf9d-98b495268244/sheets/fc187b76-79eb-4184-bf9d-98b495268244_2d999083-617b-4407-8af0-8bb727630529?#

After Lucence 10.1 is merged into 3.1, now the number has regressed. Nightly shows 630->889ms.

Personal testing shows the same:

Metric Task Value Unit
Segment count 10
90th percentile service time cardinality-agg-high 1096.88 ms

Related component

Search:Performance

To Reproduce

  1. Set concurrent search to auto
curl -X PUT "http://localhost:9200/big5/_settings" -H 'Content-Type: application/json' -d'
{
  "settings": {
    "search": {
      "concurrent_segment_search": {
        "mode": "auto"
      }
    }
  }
}
'
  1. Index big5 workload using main branch
opensearch-benchmark execute-test --pipeline=benchmark-only --workload=big5 --target-hosts=localhost:9200 --kill-running-processes   --workload-param "distribution_version:2.11.0"
  1. Run opensearch-benchmark execute-test --pipeline=benchmark-only --workload=big5 --target-hosts=localhost:9200 --kill-running-processes --workload-param "max_num_segments:10,distribution_version:3.1.0" --include-tasks="cardinality-agg-high"

Expected behavior

No change in latency

Additional Details

Plugins
No plugins enabled

Screenshots
n/a

Host/Environment (please complete the following information):

  • Tested using r5.xl host with EBS Gp3 16000 IOPS, 500Gb and 1000 throughput.
  • al2023-ami-2023.6.20250303.0-kernel-6.1-x86_64

Additional context
No

Metadata

Metadata

Assignees

Type

No type

Projects

Status

🆕 New

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions