Re: off heap indexes - setSqlOnheapRowCacheSize - how does it improve efficiency ?

In general Ignite is designed to be used in a distributed environment when gigabytes or terabytes of dataset is spread across many cluster nodes and SQL queries executed across the cluster should be faster since resources of all the machines will be used and as a result a query should be

Re: Cluster Formation between nodes in different data centers

Hi, I tried the option you told me. But it dint work. It happened to do the same thing again. So can i use the cloud based configuration. My machines are in open-stack i think it should be the public/private address issue. https://apacheignite.readme.io/v1.6/docs/generic-cloud-configuration If

Re: off heap indexes - setSqlOnheapRowCacheSize - how does it improve efficiency ?

+==+ | Node ID8(@), IP | CPUs | Heap Used | CPU Load | Up Time | Size | Hi/Mi/Rd/Wr | +==+ |

Downsides of Spark-Ignite for extended cache management and access?

My company provides big data analytics for large banks (managing and analyzing their loan portfolios). We have a number of applications that are fundamentally grid-based, but which tend to use different frameworks to handle grid computation. We are considering shifting these to a common Hadoop

Re: Unexpexted exception

Hi, I downloaded version 1.6.0 from https://ignite.apache.org/download.cgi and all is working! :) What was wrong? Thanks for your help! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unexpexted-exception-tp4847p5150.html Sent from the Apache Ignite Users

Re: off heap indexes - setSqlOnheapRowCacheSize - how does it improve efficiency ?

firstly, look at fragment of my config clieny file that bother me: 2016-05-24 15:22 GMT+02:00 Alexei

Re: off heap indexes - setSqlOnheapRowCacheSize - how does it improve efficiency ?

Have you configured near cache on the client? Do you buffer data somewere ? Share the details of the loading process. 2016-05-24 16:07 GMT+03:00 Tomek W : > Thanks for you answer. > > > I didn't measure it. Simply, I was getting GC overflow error, so I > succesively

Re: off heap indexes - setSqlOnheapRowCacheSize - how does it improve efficiency ?

Thanks for you answer. I didn't measure it. Simply, I was getting GC overflow error, so I succesively increased it. How to measure it ? Why client requires so much memory ? 2016-05-24 14:28 GMT+02:00 Alexei Scherbakov : > Just use this: > > -server -Xms10G -Xmx10G

Re: off heap indexes - setSqlOnheapRowCacheSize - how does it improve efficiency ?

Just use this: -server -Xms10G -Xmx10G -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:NewSize=128m -XX:MaxNewSize=128m -XX:MaxTenuringThreshold=0 -XX:SurvivorRatio=1024 -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=60 -XX:+DisableExplicitGC How do you measure

Re: off heap indexes - setSqlOnheapRowCacheSize - how does it improve efficiency ?

Try to start with some larger number, if default value is too low for you. On example, set it to 5, and see if the performance is OK. If not, increase to 10 etc. I can't help you further without knowing your data access patterns. BTW, for 10G heap it is probably better to use

Re: Nodes running on different operating systems

Thanks for the suggestion, but unfortunately it makes no difference. All three nodes are now using the same configuration, except that I've put each machine's local IP address at the top of the list: http://www.springframework.org/schema/beans;

Re: Clear cache from Visor throws an exception

Yes, I am planning to upgrade soon to the latest 1.6 release, and keep you updated on the the issue. Thank you. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Clear-cache-from-Visor-throws-an-exception-tp4848p5137.html Sent from the Apache Ignite Users mailing

Re: What does SPI stand for?

Hi, SPI stands for Service Provider Interface. In Ignite it is an isolated abstracted component which can be plugged in to provide new or replace/extend existing functionality. For example, you can implement your own CollisionSPI to control how ComputeJobs are scheduled on a local node, or