BTW, What if we expose per-query metrics below as a part of EXPLAIN ANALYZE? Sergi, is this feasible?
— Denis > On Feb 27, 2017, at 2:35 PM, Denis Magda <[email protected]> wrote: > > Igniters, > > Let’s shed more light on SQL query execution internals introducing a set of > useful metrics (https://issues.apache.org/jira/browse/IGNITE-4757). > > Per-query metrics. Total history size is defined by > *CacheConfiguration.getQueryDetailMetricsSize*: > * if a query was executed in the collocated or non-collocated mode. Three > results are valid: collocated, non-collocated, simple query (no joins). > * non-collocated query: size of the data exchanged between the nodes to > complete a join. > * non-collocated query: did a query do broadcast or unicast to get data > needed to complete a join. > * non-collocated and collocated query: a part of the time spent joining the > data. > > CacheMetrics: > * an average number of executed SQL queries (collocated, non-collocated, > simple query (no joins)). > > Please don’t hesitate do share suggest another metrics or improve proposed > ones. > > — > Denis
