Hi all,
i have a weird (at least in my oppinion) situation on my environment.
my hardware:
3 data nodes with 32GB of ram (16GB of Java heap for ES)
using data from logstash, stored per day manner
with 360 5shard + 1 replica indexes - NO ROUTING -> grouped by alias
named norouting*
and same indexes (different names of course) reindexed with new mapping:
and 360 4shard + 1 replica indexes - WITH ROUTING * -> grouped by alias
named routing
about 2 billions of docs,
about 0.8 TB of data
I have 4 customers that I want to split to their own indices by routing to
increase performance when querying the whole year of data.
3 customers are similar size, and one is about 2x times larger than others.
When I performed tests (I cleared the cache with _cache/clear before each
query)
Simple query that I was using for indexes with routing:
/routing/_search?routing=CUSTOMER1
{
"query": {
"filtered": {
"query": {
"match_all": {}
},
"filter": {
"term": {
"Customer.raw": "CUSTOMER1"
}
}
}
}
}
result: 360 indices read, 18 sec response
and the indexes without routing
/norouting/_search
{
"query": {
"filtered": {
"query": {
"match_all": {}
},
"filter": {
"term": {
"Customer.raw": "CUSTOMER1"
}
}
}
}
}
result: 1800 indices read, 7 sec response
... no matter which customer I want to find, results are similar,
searching with routing is always almoust 2.5 times slower !
This does not make any sense ... should be opposite in my oppinion.
Any help would be much appreciated !. After I've read about routing I was
happy and hoping I could speed up the queries without adding additional
hardware ... now I'm very sceptical.
--
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/eb1ab06d-f738-4b5e-a333-710f3b26b30a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.