aderm commented on issue #4291: Improve ES query performance
URL: https://github.com/apache/skywalking/issues/4291#issuecomment-585039094
agree, maybe can choose a suitable scenario for large data volumes. But for
using filters, the occupation of ES-side resources has not been evaluated
aderm commented on issue #4291: Improve ES query performance
URL: https://github.com/apache/skywalking/issues/4291#issuecomment-584415398
Ok, no problem
This is an automated message from the Apache Git Service.
To respond to
aderm commented on issue #4291: Improve ES query performance
URL: https://github.com/apache/skywalking/issues/4291#issuecomment-584140193
agree, It looks like this at the moment.
This is an automated message from the Apache
aderm commented on issue #4291: Improve ES query performance
URL: https://github.com/apache/skywalking/issues/4291#issuecomment-584063442
### Based on the previous situation, a 60W test data was created.
aderm commented on issue #4291: Improve ES query performance
URL: https://github.com/apache/skywalking/issues/4291#issuecomment-581005325
> I am a little confused, the score of `testFixEsFilterQuery` is higher than
`testDynamicEsFilterQuery`
The comparison of testDynamicEsQuery and
aderm commented on issue #4291: Improve ES query performance
URL: https://github.com/apache/skywalking/issues/4291#issuecomment-580990054
Use index **service_inventory** as test data. Index mapping structure is
unchanged. Constructed test document data totals 91002 and 255002.
The test
aderm commented on issue #4291: Improve ES query performance
URL: https://github.com/apache/skywalking/issues/4291#issuecomment-579833364
> Do you have benchmark, document or blogs to verify this change?
OK, some bench test examples will be executed next
