Hi,
I'm facing a performance issue with some aggregations I perform, and I need
your help if possible:
I have to documents, the *request* and the *event*. The request is the
parent of the event. Below is a (sample) mapping
event : {
dynamic : strict,
_parent : {
type : request
Can you show us what your request looks like? (including query and aggs)
On Fri, Jun 13, 2014 at 9:09 AM, Thomas thomas.bo...@gmail.com wrote:
Hi,
I'm facing a performance issue with some aggregations I perform, and I
need your help if possible:
I have to documents, the *request* and the
Below is an example aggregation i perform, is there any optimizations I can
perform? Maybe disabling some features i do not need etc.
curl -XPOST
http://localhost:9200/logs-idx.20140613/event/_search?search_type=count; -d
'
{
aggs: {
f1: {
filter: {
or: [
{
Is this request only about getting aggregations? If so you would probably
get better response times by putting the filter in the query part (under a
filtered query) and only having the date histogram in the aggregation. The
reason is that aggregations are computed on matches, and in case the query
So I restructured my curl as follows, is this what you mean?, by doing some
first hits i do get some slight improvement, but need to check into
production data:
Thank you will try it and come back with results
curl -XPOST
Indeed that is what I meant.
On Fri, Jun 13, 2014 at 10:33 AM, Thomas thomas.bo...@gmail.com wrote:
So I restructured my curl as follows, is this what you mean?, by doing
some first hits i do get some slight improvement, but need to check into
production data:
Thank you will try it and
