Kibana version: 7.17.3
Elasticsearch version: 7.17.3
APM Server version: 7.17.3
APM Agent language and version: Java 1.33.0
Browser version: Chrome 100+
Original install method (e.g. download page, yum, deb, from source, etc.) and version: zip
Fresh install or upgraded from other version? Fresh
Is there anything special in your setup? simple
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
I found kibana's "traces" menu under APM is extremely slow while opening, if there are over 8000 trace keys and set the time range to "last 7 days", without any other kquery, like first click.
From what i can see, the backend of kibana, there is one node thread consuming 100%cpu all the time while opening that page, but es monitor data seems ok. what's worse is that all other requests are blocked until the node thread become normal.
I made some cpu profile, and found the root cause maybe at "x-pack/plugins/apm/common/utils/join_by_key/index.ts#L61", while calling "isEqual" of lodash. This function performance bad.
may be we could try choosing some other tools?
Steps to reproduce:
- prepare some apm data, like 20 services and 8000 trace keys
- open kibana, navigate to "traces"
- boom!
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
