-
Notifications
You must be signed in to change notification settings - Fork 24.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
field collapsing very slow #24900
Comments
how many hits are you asking for? |
and how well distributed are your collapse field values. it has to keep pulling hits until it finds and are you asking for inner hits as well? that's why we ask for a recreation |
my doc count: 12000 this my collapse DSL:
|
how many hits are you asking for? my hits.total 1130 |
You don't say how what you set Your collapsed query is doing much more work than your other query, so it is not surprising it is slower |
@zplzpl the |
query size:36 Thank you for reply. |
The took time computed for search requests does not take in account the expand search phase. This change delays the computation to after the expand phase finishes. Relates elastic#24900
The took time computed for search requests does not take in account the expand search phase. This change delays the computation to after the expand phase finishes. Relates #24900
The took time computed for search requests does not take in account the expand search phase. This change delays the computation to after the expand phase finishes. Relates #24900
Elasticsearch version: v5.3.2
Plugins installed: [ik,pinyin]
JVM version (
java -version
): openjdk version "1.8.0_121"OS version (
uname -a
if on a Unix-like system): Linux es1 2.6.32-431.11.25.el6.ucloud.x86_64 #1 SMP Tue Jul 19 10:06:12 EDT 2016 x86_64 x86_64 x86_64 GNU/LinuxDescription of the problem including expected versus actual behavior:
Only one field is used to collapsing . the field type is keyword.
hits.total = 1130
The same request does not contain the collapsing that are only used for 13 milliseconds, using a collapsing using 130 milliseconds. (This time is CURL starttransfer time)
10x time.
Using the restful api.
The text was updated successfully, but these errors were encountered: