Versions (relevant - OpenSearch/Dashboard/Server OS/Browser): 2.15, 3.4
Describe the issue: Running the same performance tests, OpenSearch is now using almost double the amount of memory. This is causing us to hit circuit breakers we’ve never hit before on 2.15. Setting the real memory flag to false seems to be a semi work around, but we understand the potential pitfalls with this and would like to keep said flag at true if at all possible.
We have discovered that aggregate queries seem to not play well and do spike the memory usage quite a bit. We test without any aggregate queries we do get a lot more queries ran without hitting said circuit breaker.
Configuration: Docker containers with a simple console app running 12 threads querying opensearch with a variety of queries.
200k docs
1G heap which is default for the docker container (I understand that is low, however, the point is 2.15 handles this load without circuit breaking and 3.x’s whole thing is performance and better usage of space and memory…)
Relevant Logs or Screenshots: