Re:Re: Re: Fetched result use too much time

2017-10-11 Thread Lucky
My ignite version is 2.2. 在 2017-10-10 20:58:55,"Andrey Mashenkov" 写道: Hi Lucky, Looks like your query selectivity is poor and even with GroupBy large amount of data shoud be fetched to reduce node. 1. Is it possiblt to coolocate data on field used in

Re: Re: Fetched result use too much time

2017-10-10 Thread Andrey Mashenkov
Hi Lucky, Looks like your query selectivity is poor and even with GroupBy large amount of data shoud be fetched to reduce node. 1. Is it possiblt to coolocate data on field used in OrderBy clause? 2. Looks weird that queryParallelizm cause wrong results. Looks like you have a single node grid

Re:Re: Fetched result use too much time

2017-10-10 Thread Lucky
Andrey Mashenkov Thank you very much! 1.query parallelism:this will cause a problem: fetch wrong reslut. I set it to 10,and have table a with 150,000 records, table b with 12,000,000 records. when I query single table,the result is correct. but when the sql is like

回复: Fetched result use too much time

2017-09-21 Thread Lucky
Andrey Mashenkov Thank you very much! 1.query parallelism:this will cause a problem: fetch wrong reslut. I set it to 10,and have table a with 150,000 records, table b with 12,000,000 records. when I query single table,the result is correct. but when the sql is like

Re: Fetched result use too much time

2017-09-21 Thread Andrey Mashenkov
Lucky, 1. Looks like it make no sense to set query parallelism level higher number of available CPU on node. 2. Map query use index for field FASSIGCUID type of String and seems values are 16 chars length strings (32 bytes) By default, values with size < 10 bytes can be inlined in index, so

回复: Fetched result use too much time

2017-09-18 Thread Lucky
Please see the attachment. I have set query parallelism to 30. it took 42 seconds. But it is not enough. I excepted it took less than 3 seconds. then,I have 3 nodes. As for the 3589 number, we need to check the number of ID using in conditions. Only the number of times used is equal to the

Re: Re: Fetched result use too much time

2017-09-16 Thread Dmitriy Setrakyan
Lucky, We would like to see the output of the "EXPLAIN" command for the query that takes a long time, so we could make suggestions. Can you post it here? D. On Fri, Sep 15, 2017 at 11:50 PM, Lucky wrote: > Hi , Yakov Zhdanov > Actually I did not run H2 console, I run

Re:Re: Fetched result use too much time

2017-09-16 Thread Lucky
Hi , Yakov Zhdanov Actually I did not run H2 console, I run like this : cache.query(newSqlFieldsQuery("explain select id from assignInfo ")); I change to like this: newSqlFieldsQuery("select * from Person p join table(id bigint = ?) i on p.id =

Re: Fetched result use too much time

2017-09-15 Thread Yakov Zhdanov
Please run explain from Ignite, not from H2 console - https://apacheignite.readme.io/docs/sql-performance-and-debugging#using-explain-statement Here you can find info on proper IN usage in Ignite -