Querying on multiple types


(Jinal Shah) #1

Hi,

I have a question regarding the performance when elastic search query is
executed over multiple types (for example 15) opposed to single type.

If I run the following 2 queries on 10 million records, could someone give
me the performance comparison or the execution flow of the queries?

Query 1:
http://elasticsearch.server.com/index1/type1/_search?q=id:QW12ER

Query 2:
http://elasticsearch.server.com/index1/type1,type2,type3,type4,type5,type6,type7,type8,type9,type10,type11,type12,type13,type14,type15/_search?q=id:QW12ER

The scenario I am trying to understand is, how much would be the
performance hit if I try to run a query on multiple types.

Thanks in advance.

Cheers,
Jinal

--
The information contained in this e-mail message and any accompanying files
is or may be confidential. If you are not the intended recipient, any use,
dissemination, reliance, forwarding, printing or copying of this e-mail or
any attached files is unauthorised. This e-mail is subject to copyright. No
part of it should be reproduced, adapted or communicated without the
written consent of the copyright owner. If you have received this e-mail in
error please advise the sender immediately by return e-mail or telephone
and delete all copies. Fairfax Media does not guarantee the accuracy or
completeness of any information contained in this e-mail or attached files.
Internet communications are not secure, therefore Fairfax Media does not
accept legal responsibility for the contents of this message or attached
files.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f514e51d-b911-4bcd-b688-b05122aa6ade%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Boaz Leskes) #2

Hi Jinal,

The overhead is marginal. ES initially constructs a filter based on the
incoming types and uses that while searching. The result of that fitler iis
also cached, so repetitive usage has even less overhead.

Note though that you will be search more data, so underlying query may take
longer simple by having to analyze more documents. However, roughly
speaking, querying one type with 1M docs is roughly identical to querying
10 types with 100K docs each.

Cheers,
Boaz

On Tuesday, February 18, 2014 4:55:08 AM UTC+1, Jinal Shah wrote:

Hi,

I have a question regarding the performance when elastic search query is
executed over multiple types (for example 15) opposed to single type.

If I run the following 2 queries on 10 million records, could someone give
me the performance comparison or the execution flow of the queries?

Query 1:
http://elasticsearch.server.com/index1/type1/_search?q=id:QW12ER

Query 2:

http://elasticsearch.server.com/index1/type1,type2,type3,type4,type5,type6,type7,type8,type9,type10,type11,type12,type13,type14,type15/_search?q=id:QW12ER

The scenario I am trying to understand is, how much would be the
performance hit if I try to run a query on multiple types.

Thanks in advance.

Cheers,
Jinal

The information contained in this e-mail message and any accompanying
files is or may be confidential. If you are not the intended recipient, any
use, dissemination, reliance, forwarding, printing or copying of this
e-mail or any attached files is unauthorised. This e-mail is subject to
copyright. No part of it should be reproduced, adapted or communicated
without the written consent of the copyright owner. If you have received
this e-mail in error please advise the sender immediately by return e-mail
or telephone and delete all copies. Fairfax Media does not guarantee the
accuracy or completeness of any information contained in this e-mail or
attached files. Internet communications are not secure, therefore Fairfax
Media does not accept legal responsibility for the contents of this message
or attached files.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5896d6f8-8378-452e-aa7c-4a84767adc28%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Jinal Shah) #3

Hi Boaz,

Thanks for the information.

Cheers,
Jinal

On Tuesday, 18 February 2014 23:34:18 UTC+11, Boaz Leskes wrote:

Hi Jinal,

The overhead is marginal. ES initially constructs a filter based on the
incoming types and uses that while searching. The result of that fitler iis
also cached, so repetitive usage has even less overhead.

Note though that you will be search more data, so underlying query may
take longer simple by having to analyze more documents. However, roughly
speaking, querying one type with 1M docs is roughly identical to querying
10 types with 100K docs each.

Cheers,
Boaz

On Tuesday, February 18, 2014 4:55:08 AM UTC+1, Jinal Shah wrote:

Hi,

I have a question regarding the performance when elastic search query is
executed over multiple types (for example 15) opposed to single type.

If I run the following 2 queries on 10 million records, could someone
give me the performance comparison or the execution flow of the queries?

Query 1:
http://elasticsearch.server.com/index1/type1/_search?q=id:QW12ER

Query 2:

http://elasticsearch.server.com/index1/type1,type2,type3,type4,type5,type6,type7,type8,type9,type10,type11,type12,type13,type14,type15/_search?q=id:QW12ER

The scenario I am trying to understand is, how much would be the
performance hit if I try to run a query on multiple types.

Thanks in advance.

Cheers,
Jinal

The information contained in this e-mail message and any accompanying
files is or may be confidential. If you are not the intended recipient, any
use, dissemination, reliance, forwarding, printing or copying of this
e-mail or any attached files is unauthorised. This e-mail is subject to
copyright. No part of it should be reproduced, adapted or communicated
without the written consent of the copyright owner. If you have received
this e-mail in error please advise the sender immediately by return e-mail
or telephone and delete all copies. Fairfax Media does not guarantee the
accuracy or completeness of any information contained in this e-mail or
attached files. Internet communications are not secure, therefore Fairfax
Media does not accept legal responsibility for the contents of this message
or attached files.

--
The information contained in this e-mail message and any accompanying files
is or may be confidential. If you are not the intended recipient, any use,
dissemination, reliance, forwarding, printing or copying of this e-mail or
any attached files is unauthorised. This e-mail is subject to copyright. No
part of it should be reproduced, adapted or communicated without the
written consent of the copyright owner. If you have received this e-mail in
error please advise the sender immediately by return e-mail or telephone
and delete all copies. Fairfax Media does not guarantee the accuracy or
completeness of any information contained in this e-mail or attached files.
Internet communications are not secure, therefore Fairfax Media does not
accept legal responsibility for the contents of this message or attached
files.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d4e1565d-dd84-416b-b022-6e295540754a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #4