You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Kevin Daly <ke...@meta.com> on 2016/04/21 17:42:59 UTC
Best Practices for Deploying Ignite
I'm just wondering if I am deploying Ignite to Hardware let's say with 128GB
RAM on each node.. Is it best to have just one ignite process run on the
machine and use the entire machine.. Or should I run multiple ignite
processes on the same machine?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Best-Practices-for-Deploying-Ignite-tp4417.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Best Practices for Deploying Ignite
Posted by Jörn Franke <jo...@gmail.com>.
In Addition to that you should make sure that you run JDK8, it has a lot of optimizations
> On 21 Apr 2016, at 21:06, vkulichenko <va...@gmail.com> wrote:
>
> In most cases it's OK to have one node per machine, but you should not
> allocate more than 10-12G of heap memory, because otherwise you will likely
> have long GC pauses. For storing the data you can use off-heap memory [1].
>
> The only case when having several nodes per machine can be useful is when
> SQL queries are heavily used. If each node has less data, the SQL query
> execution can scale better and give better performance. Essentially, you
> will just better use CPU resources, so it's a good practice to start as many
> nodes as many cores you have.
>
> [1] https://apacheignite.readme.io/docs/off-heap-memory
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Best-Practices-for-Deploying-Ignite-tp4417p4426.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Best Practices for Deploying Ignite
Posted by vkulichenko <va...@gmail.com>.
In most cases it's OK to have one node per machine, but you should not
allocate more than 10-12G of heap memory, because otherwise you will likely
have long GC pauses. For storing the data you can use off-heap memory [1].
The only case when having several nodes per machine can be useful is when
SQL queries are heavily used. If each node has less data, the SQL query
execution can scale better and give better performance. Essentially, you
will just better use CPU resources, so it's a good practice to start as many
nodes as many cores you have.
[1] https://apacheignite.readme.io/docs/off-heap-memory
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Best-Practices-for-Deploying-Ignite-tp4417p4426.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.