Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
> I am using one cache that having 2 lacs record in server side. when i try
> to execute query in client side that means in client mode that time time
> is taken long time (more than two mins) and also some time system is
> getting corrupted .
> My system configuration is 3gb ram and Ignite server configuration is 7gb
> consider cache configuration :
> CacheConfiguration<Integer, TopUniqueFirewall> cfg = new
> CacheConfiguration<Integer, TopUniqueFirewall>();
> cfg.setEvictionPolicy(new FifoEvictionPolicy(5000));
> cfg.setIndexedTypes(Integer.class, TopUniqueFirewall.class);
> // Create cache with given name, if it does not exist.
> IgniteCache<Integer, TopUniqueFirewall>
> insertTopUniqueFirewallCache = ignite.getOrCreateCache(cfg);
> Query is
> select src_ip as src_ip,src_name
> as src_name,dst_ip as dst_ip,dst_name as dst_name, dst_port as
> dst_port,service_name as service_name,sum(count) as count,
> sum(recv_bytes) as inbytes,
> sum(sent_bytes) as outbytes, (sum(sent_bytes)+sum(recv_bytes))
> total, sum(recv_pkt) as inpacket, sum(sent_pkt) as outpacket,
> sum(duration) as duration from
> "topUniqueFirewallCache".TopUniqueFirewall as
> t where (src_ip > 0 or src_name != 'N/A') and (dst_ip > 0 or
> dst_name !=
> 'N/A') group by
> order by count desc limit 10
> Please give performance to increase execution sqlfield query
There are at least two possible reasons.
First is memory issues. You should make sure that you're not running out of
memory and that there are no long GC pauses. Refer to  for details. Also
I'm confused by this statement: "My system configuration is 3gb ram and
Ignite server configuration is 7gb ram." What is meant by that? Are you
trying to allocate more memory than you physically have? If so, you can get
a lot of unpredictable issues.
Second is inefficient indexing and unoptimized query. I would start with
running EXPLAIN  for your query and looking at the execution plan. You
should try to avoid any scans and use indexes where possible.
View this message in context:
Sent from the Apache Ignite Users mailing list archive at Nabble.com.