Hi Evgenii,
Thank you for suggesting the query optimization. It worked perfectly fine.
I unnecessarily complicated the sql.
I really appreciate the efforts you guys are taking to help out the users.
About the test data: Yes in production I will be having more than 100K
records for single
Well, looks like you trying to find the segments that intersects defined
segment, but you're complicating it. You don't need 3 conditions here - it
will be enough to have only one - ipStart <= MAX and ipEnd >= MIN. I've
checked it for your case and got absolutely the same results as you have
with
Hi Evgenii,
Did you get time to check the reproducer?
Can you please suggest solution for this?
Thanks,
Prasad
On Fri, Oct 19, 2018, 4:46 PM Prasad Bhalerao
wrote:
> Hi Evgenii,
>
> I have created a reproducer and uploaded it to GitHub. I have created 5
> cases to test the sql execution
Hi Evgenii,
I have created a reproducer and uploaded it to GitHub. I have created 5
cases to test the sql execution time.
GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git
Please run IgniteQueryTester class.
Thanks,
Prasad
On Wed, Oct 17, 2018 at 7:46 PM ezhuravlev
How much data do you have? What is the amount of heap and offheap memory?
Can you share the reproducer with the community?
Evgenii
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, Evgenii,
I tried to execute sql without UNION ALL operator. I mean I just executed
the first part of the sql as shown below and it is taking 700-800 ms to
complete. I have around 3 million records in my cache. and will be having
around 30-40 million records in real scenario.
SELECT id,
Hi,
What is the execution time of just a single query without UNION?
Evgenii
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
there any solution for this?
> Can someone please respond?
>
> Thanks,
> Prasad
>
>
> -- Forwarded message -
> From: Prasad Bhalerao
> Date: Fri, Sep 7, 2018, 8:04 AM
> Subject: Fwd: Query execution too long even after providing index
> To:
>
>
> C
Guys, is there any solution for this?
Can someone please respond?
Thanks,
Prasad
-- Forwarded message -
From: Prasad Bhalerao
Date: Fri, Sep 7, 2018, 8:04 AM
Subject: Fwd: Query execution too long even after providing index
To:
Can we have update
Can we have update on this?
-- Forwarded message -
From: Prasad Bhalerao
Date: Wed, Sep 5, 2018, 11:34 AM
Subject: Re: Query execution too long even after providing index
To:
Hi Andrey,
Can you please help me with this? I
Thanks,
Prasad
On Tue, Sep 4, 2018 at 2:08 PM Prasad
Hi Andrey,
Can you please help me with this? I
Thanks,
Prasad
On Tue, Sep 4, 2018 at 2:08 PM Prasad Bhalerao
wrote:
>
> I tried changing SqlIndexMaxInlineSize to 32 byte and 100 byte using cache
> config.
>
> ipContainerIpV4CacheCfg.setSqlIndexMaxInlineSize(32/100);
>
> But it did not improve
I tried changing SqlIndexMaxInlineSize to 32 byte and 100 byte using cache
config.
ipContainerIpV4CacheCfg.setSqlIndexMaxInlineSize(32/100);
But it did not improve the sql execution time. Sql execution time increases
with increase in cache size.
It is a simple range scan query. Which part of
HI,
Have you tried to increase index inlineSize? It is 10 bytes by default.
Your indices uses simple value types (Java primitives) and all columns can
be easily inlined.
It should be enough to increase inlineSize up to 32 bytes (3 longs + 1 int
= 3*(8 /*long*/ + 1/*type code*/) + (4/*int*/ +
Hi,
My cache has 1 million rows and the sql is as follows.
This sql is taking around 1.836 seconds to execute and this time increases
as I go on adding the data to this cache. Some time it takes more than 4
seconds.
Is there any way to improve the execution time?
*SQL:*
SELECT id,
14 matches
Mail list logo
