[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[
https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857821#comment-15857821
]
Vyacheslav Daradur edited comment on IGNITE-4374 at 2/8/17 12:33 PM:
-
[~dmagda]
Done.
Current output:
{code}
[11:54:40]
[11:54:41] Message queue limit is set to 0 which may lead to potential OOMEs
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
message queues growth on sender and receiver sides.
[11:54:41] Security status [authentication=off, tls/ssl=off]
[11:54:43] Performance suggestions for grid (fix if possible)
[11:54:43] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[11:54:43] ^-- JVM heap size is greater than 30.5Gb, JVM will not use
compressed oops
[11:54:43] ^-- Enable server mode for JVM (add '-server' to JVM options)
[11:54:43] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM options)
[11:54:43] ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to
JVM options)"
[11:54:43] ^-- Specify New I/O max total size (add
'-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
[11:54:43] ^-- Enable the thread-local allocation blocks (add '-XX:+UseTLAB'
to JVM options)
[11:54:43] ^-- Disable processing of calls to System.gc() (add
'-XX:+DisableExplicitGC' to JVM options)
[11:54:43] ^-- Speed up flushing of dirty pages by OS (alter
vm.dirty_writeback_centisecs and vm.dirty_expire_centisecs parameters by
setting to 500)
[11:54:43] ^-- Reduce pages swapping ratio (set vm.swappiness=10)
[11:54:43] ^-- Disable NUMA memory reclaim (set vm.zone_reclaim_mode=0)
[11:54:43] ^-- Avoid direct reclaim and page allocation failures (set
vm.extra_free_kbytes=124)
[11:54:43] Refer to this page for more performance suggestions:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[11:54:43]
[11:54:43] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[11:54:43]
[11:54:43] Ignite node started OK (id=8bf18ef1)
[11:54:43] Topology snapshot [ver=1, servers=1, clients=0, CPUs=1, heap=1.0GB]
{code}
These lines are optionaly:
{code}
[11:59:07] ^-- Speed up flushing of dirty pages by OS (alter
vm.dirty_expire_centisecs parameter by setting to 500)
or
[12:34:01] ^-- Speed up flushing of dirty pages by OS (alter
vm.dirty_writeback_centisecs parameter by setting to 500)
or
[12:33:01] ^-- Speed up flushing of dirty pages by OS (alter
vm.dirty_writeback_centisecs and vm.dirty_expire_centisecs parameters by
setting to 500)
{code}
bq. Avoid direct reclaim and page allocation failures (set vm.extra_free_kbytes
to 124 or other value).
We check equality to 124. If we write "or other value", we should change
the check and the article.
[Latest ci.tests|http://ci.ignite.apache.org/viewQueued.html?itemId=449798]
was (Author: daradurvs):
[~dmagda]
Done.
Current output:
{code}
[11:54:40]
[11:54:41] Message queue limit is set to 0 which may lead to potential OOMEs
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
message queues growth on sender and receiver sides.
[11:54:41] Security status [authentication=off, tls/ssl=off]
[11:54:43] Performance suggestions for grid (fix if possible)
[11:54:43] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[11:54:43] ^-- JVM heap size is greater than 30.5Gb, JVM will not use
compressed oops
[11:54:43] ^-- Enable server mode for JVM (add '-server' to JVM options)
[11:54:43] ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM options)
[11:54:43] ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to
JVM options)"
[11:54:43] ^-- Specify New I/O max total size (add
'-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
[11:54:43] ^-- Enable the thread-local allocation blocks (add '-XX:+UseTLAB'
to JVM options)
[11:54:43] ^-- Disable processing of calls to System.gc() (add
'-XX:+DisableExplicitGC' to JVM options)
[11:54:43] ^-- Speed up flushing of dirty pages by OS (alter
vm.dirty_writeback_centisecs and vm.dirty_expire_centisecs parameters by
setting to 500)
[11:54:43] ^-- Reduce pages swapping ratio (set vm.swappiness=10)
[11:54:43] ^-- Disable NUMA memory reclaim (set vm.zone_reclaim_mode=0)
[11:54:43] ^-- Avoid direct reclaim and page allocation failures (set
vm.extra_free_kbytes=124)
[11:54:43] Refer to this page for more performance suggestions:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[11:54:43]
[11:54:43] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[11:54:43]
[11:54:43] Ignite node started OK (id=8bf18ef1)
[11:54:43] Topology snapshot [ver=1, servers=1, clients=0, CPUs=1, heap=1.0GB]
{code}
These lines are optionaly:
{code}
[11:59:07] ^-- Speed up flushing of dirty pages by OS (alter
vm.dirty_expire_centisecs parameter by setting to 500)
or
[12:34:01] ^-- Speed up flushing of dirty pages by OS
[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[
https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856819#comment-15856819
]
Vyacheslav Daradur edited comment on IGNITE-4374 at 2/8/17 7:38 AM:
[~dmagda],
What about dot at the end at the existing suggestions?
WIll i add?
{code}
"Disable collision resolution (remove 'collisionSpi' from configuration)"
"Disable checkpoints (remove 'checkpointSpi' from configuration)"
"Disable local jobs marshalling (set 'marshalLocalJobs' to false)"
"Disable grid events (remove 'includeEventTypes' from configuration)"
"Use default binary marshaller (do not set 'marshaller' explicitly)"
{code}
was (Author: daradurvs):
[~dmagda],
What about dots on the end at the existing suggestions?
WIll i add?
{code}
"Disable collision resolution (remove 'collisionSpi' from configuration)"
"Disable checkpoints (remove 'checkpointSpi' from configuration)"
"Disable local jobs marshalling (set 'marshalLocalJobs' to false)"
"Disable grid events (remove 'includeEventTypes' from configuration)"
"Use default binary marshaller (do not set 'marshaller' explicitly)"
{code}
> Ignite should validate JVM and OS configuration and output warning in log
> -
>
> Key: IGNITE-4374
> URL: https://issues.apache.org/jira/browse/IGNITE-4374
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Yakov Zhdanov
>Assignee: Vyacheslav Daradur
> Attachments: x32_not_optimized.png, x32_optimized.png,
> x64_not_optimized.png, x64_optimized.png
>
>
> Currently we have GridPerformanceSuggestions that output suggestions to logs
> on Ignite start on how Ignite can be improved.
> I suggest to go a little bit deeper and validate more configuration options
> and add validation for JVM and OS settings.
> Ignite should output warning if:
> * GC logging is not enabled
> * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
> * Heap size is greater than 30,5G and JVM cannot use compressed oops
> * Any of the recommended OS setting described here
> https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly
> set
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[
https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856819#comment-15856819
]
Vyacheslav Daradur edited comment on IGNITE-4374 at 2/7/17 9:27 PM:
[~dmagda],
What about dots on the end at the existing suggestions?
WIll i add?
{code}
"Disable collision resolution (remove 'collisionSpi' from configuration)"
"Disable checkpoints (remove 'checkpointSpi' from configuration)"
"Disable local jobs marshalling (set 'marshalLocalJobs' to false)"
"Disable grid events (remove 'includeEventTypes' from configuration)"
"Use default binary marshaller (do not set 'marshaller' explicitly)"
{code}
was (Author: daradurvs):
[~dmagda],
How about dots on the end at the existing suggestions?
WIll i add?
{code}
"Disable collision resolution (remove 'collisionSpi' from configuration)"
"Disable checkpoints (remove 'checkpointSpi' from configuration)"
"Disable local jobs marshalling (set 'marshalLocalJobs' to false)"
"Disable grid events (remove 'includeEventTypes' from configuration)"
"Use default binary marshaller (do not set 'marshaller' explicitly)"
{code}
> Ignite should validate JVM and OS configuration and output warning in log
> -
>
> Key: IGNITE-4374
> URL: https://issues.apache.org/jira/browse/IGNITE-4374
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Yakov Zhdanov
>Assignee: Vyacheslav Daradur
> Attachments: x32_not_optimized.png, x32_optimized.png,
> x64_not_optimized.png, x64_optimized.png
>
>
> Currently we have GridPerformanceSuggestions that output suggestions to logs
> on Ignite start on how Ignite can be improved.
> I suggest to go a little bit deeper and validate more configuration options
> and add validation for JVM and OS settings.
> Ignite should output warning if:
> * GC logging is not enabled
> * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
> * Heap size is greater than 30,5G and JVM cannot use compressed oops
> * Any of the recommended OS setting described here
> https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly
> set
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[ https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839693#comment-15839693 ] Vyacheslav Daradur edited comment on IGNITE-4374 at 1/26/17 2:54 PM: - [~yzhdanov], [~dmagda], I like the idea to place code of checks on different classes, because they check different things and they have own output format. It is easy to add new checks. I don't like the idea to add additional sections in GridConfigurationSuggestions. I think to give just the reference to the readme.io page – is the bad idea, because if someone to change article it will be necessary to change the code. (e.g. someone remove an option from article which is checked) I think there are 2 ways: *1.* (I don't like it) 1.1 We will make output less detailed 1.2 Move JVM and OS checks to IgniteKernal 1.3 Rename GridConfigurationSuggestions to ConfigurationSugestions *2.* bq. Moreover, they use single system property to disable the output. - we can add another a class, which will control output of all suggestions; - or add another system properties to disable output of JVM and OS suggections; - or remove this flag from suggestions classes and to check it only in IgniteKernal, where we invoke #logSuggestions; -- The output example consists all checks, actually the output will be less. I need to understand what output you want to see, because I think the current output isn't overloaded. was (Author: daradurvs): [~yzhdanov], [~dmagda], I like the idea to place code of checks on different classes, because they check different things and they have own output format. It is easy to add new checks. I don't like the idea to add additional sections in GridConfigurationSuggestions. I think to give just the reference to the readme.io page – is the bad idea, because if someone to change article it will be necessary to change the code. (e.g. someone remove an option from article which is checked) I think there are 2 ways: *1.* (I don't like it) 1.1 We will make output less detailed 1.2 Move JVM and OS checks to IgniteKernal 1.3 Rename GridConfigurationSuggestions to ConfigurationSugestions *2.* bq. Moreover, they use single system property to disable the output. - we can add another a class, which will control output of all suggestions; - or add another system properties to disable output of JVM and OS suggections; - or remove this flag from suggestions classes and to check it only in IgniteKernal, where we invoke #logSuggestions; -- The output example consists all checks, actually the output will be less. I need to understand what output you want to see, because I think the current output isn't overloaded. > Ignite should validate JVM and OS configuration and output warning in log > - > > Key: IGNITE-4374 > URL: https://issues.apache.org/jira/browse/IGNITE-4374 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Yakov Zhdanov >Assignee: Vyacheslav Daradur > Attachments: x32_not_optimized.png, x32_optimized.png, > x64_not_optimized.png, x64_optimized.png > > > Currently we have GridPerformanceSuggestions that output suggestions to logs > on Ignite start on how Ignite can be improved. > I suggest to go a little bit deeper and validate more configuration options > and add validation for JVM and OS settings. > Ignite should output warning if: > * GC logging is not enabled > * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize) > * Heap size is greater than 30,5G and JVM cannot use compressed oops > * Any of the recommended OS setting described here > https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly > set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[ https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839693#comment-15839693 ] Vyacheslav Daradur edited comment on IGNITE-4374 at 1/26/17 2:54 PM: - [~yzhdanov], [~dmagda], I like the idea to place code of checks on different classes, because they check different things and they have own output format. It is easy to add new checks. I don't like the idea to add additional sections in GridConfigurationSuggestions. I think to give just the reference to the readme.io page – is the bad idea, because if someone to change article it will be necessary to change the code. (e.g. someone remove an option from article which is checked) I think there are 2 ways: *1.* (I don't like it) 1.1 We will make output less detailed 1.2 Move JVM and OS checks to IgniteKernal 1.3 Rename GridConfigurationSuggestions to ConfigurationSugestions *2.* bq. Moreover, they use single system property to disable the output. - we can add another a class, which will control output of all suggestions; - or add another system properties to disable output of JVM and OS suggections; - or remove this flag from suggestions classes and to check it only in IgniteKernal, where we invoke #logSuggestions; -- The output example consists all checks, actually the output will be less. I need to understand what output you want to see, because I think the current output isn't overloaded. was (Author: daradurvs): [~yzhdanov], [~dmagda], I like the idea to place code of checks on different classes, because they check different things and they have own output format. It is easy to add new checks. I don't like the idea to add additional sections in GridConfigurationSuggestions. I think to give just the reference to the readme.io page – is the bad idea, because if someone to change article it will be necessary to change the code. (e.g. someone remove an option from article which is checked) I think there are 2 ways: *1.* (I don't like it) 1.1 We will make output less detailed 1.2 Move JVM and OS checks to IgniteKernal 1.3 Rename GridConfigurationSuggestions to ConfigurationSugestions *2.* bq. Moreover, they use single system property to disable the output. We can add another a class, which will control output of all suggestions. Оr add another system properties to disable output of JVM and OS suggections. -- The output example consists all checks, actually the output will be less. I need to understand what output you want to see, because I think the current output isn't overloaded. > Ignite should validate JVM and OS configuration and output warning in log > - > > Key: IGNITE-4374 > URL: https://issues.apache.org/jira/browse/IGNITE-4374 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Yakov Zhdanov >Assignee: Vyacheslav Daradur > Attachments: x32_not_optimized.png, x32_optimized.png, > x64_not_optimized.png, x64_optimized.png > > > Currently we have GridPerformanceSuggestions that output suggestions to logs > on Ignite start on how Ignite can be improved. > I suggest to go a little bit deeper and validate more configuration options > and add validation for JVM and OS settings. > Ignite should output warning if: > * GC logging is not enabled > * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize) > * Heap size is greater than 30,5G and JVM cannot use compressed oops > * Any of the recommended OS setting described here > https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly > set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[ https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839693#comment-15839693 ] Vyacheslav Daradur edited comment on IGNITE-4374 at 1/26/17 2:39 PM: - [~yzhdanov], [~dmagda], I like the idea to place code of checks on different classes, because they check different things and they have own output format. It is easy to add new checks. I don't like the idea to add additional sections in GridConfigurationSuggestions. I think to give just the reference to the readme.io page – is the bad idea, because if someone to change article it will be necessary to change the code. (e.g. someone remove an option from article which is checked) I think there are 2 ways: *1.* (I don't like it) 1.1 We will make output less detailed 1.2 Move JVM and OS checks to IgniteKernal 1.3 Rename GridConfigurationSuggestions to ConfigurationSugestions *2.* bq. Moreover, they use single system property to disable the output. We can add another a class, which will control output of all suggestions. Оr add another system properties to disable output of JVM and OS suggections. -- The output example consists all checks, actually the output will be less. I need to understand what output you want to see, because I think the current output isn't overloaded. was (Author: daradurvs): [~yzhdanov], [~dmagda], I like the idea to place code of checks on different classes, because they check different things and they have own output format. I don't like the idea to add additional sections in GridConfigurationSuggestions. I think to give just the reference to the readme.io page – is the bad idea, because if someone to change article it will be necessary to change the code. (e.g. someone remove an option from article which is checked) I think there are 2 ways. *1.* 1.1 We will make output less detailed 1.2 Move JVM and OS checks to IgniteKernal 1.3 Rename GridConfigurationSuggestions to ConfigurationSugestions *2.* bq. Moreover, they use single system property to disable the output. We can add another a class, which will control output of all checks. or add another system properties to disable output of JVM and OS suggections. The output example consists all checks, actually the output will be less. I need to understand what output you want to see, because I think the current output isn't overloaded. > Ignite should validate JVM and OS configuration and output warning in log > - > > Key: IGNITE-4374 > URL: https://issues.apache.org/jira/browse/IGNITE-4374 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Yakov Zhdanov >Assignee: Vyacheslav Daradur > Attachments: x32_not_optimized.png, x32_optimized.png, > x64_not_optimized.png, x64_optimized.png > > > Currently we have GridPerformanceSuggestions that output suggestions to logs > on Ignite start on how Ignite can be improved. > I suggest to go a little bit deeper and validate more configuration options > and add validation for JVM and OS settings. > Ignite should output warning if: > * GC logging is not enabled > * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize) > * Heap size is greater than 30,5G and JVM cannot use compressed oops > * Any of the recommended OS setting described here > https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly > set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[ https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839693#comment-15839693 ] Vyacheslav Daradur edited comment on IGNITE-4374 at 1/26/17 2:29 PM: - [~yzhdanov], [~dmagda], I like the idea to place code of checks on different classes, because they check different things and they have own output format. I don't like the idea to add additional sections in GridConfigurationSuggestions. I think to give just the reference to the readme.io page – is the bad idea, because if someone to change article it will be necessary to change the code. (e.g. someone remove an option from article which is checked) I think there are 2 ways. *1.* 1.1 We will make output less detailed 1.2 Move JVM and OS checks to IgniteKernal 1.3 Rename GridConfigurationSuggestions to ConfigurationSugestions *2.* bq. Moreover, they use single system property to disable the output. We can add another a class, which will control output of all checks. or add another system properties to disable output of JVM and OS suggections. The output example consists all checks, actually the output will be less. I need to understand what output you want to see, because I think the current output isn't overloaded. was (Author: daradurvs): [~daradurvs], [~dmagda], I like the idea to place code of checks on different classes, because they check different things and they have own output format. I don't like the idea to add additional sections in GridConfigurationSuggestions. I think to give just the reference to the readme.io page – is the bad idea, because if someone to change article it will be necessary to change the code. (e.g. someone remove an option from article which is checked) I think there are 2 ways. *1.* 1.1 We will make output less detailed 1.2 Move JVM and OS checks to IgniteKernal 1.3 Rename GridConfigurationSuggestions to ConfigurationSugestions *2.* bq. Moreover, they use single system property to disable the output. We can add another a class, which will control output of all checks. or add another system properties to disable output of JVM and OS suggections. The output example consists all checks, actually the output will be less. I need to understand what output you want to see, because I think the current output isn't overloaded. > Ignite should validate JVM and OS configuration and output warning in log > - > > Key: IGNITE-4374 > URL: https://issues.apache.org/jira/browse/IGNITE-4374 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Yakov Zhdanov >Assignee: Vyacheslav Daradur > Attachments: x32_not_optimized.png, x32_optimized.png, > x64_not_optimized.png, x64_optimized.png > > > Currently we have GridPerformanceSuggestions that output suggestions to logs > on Ignite start on how Ignite can be improved. > I suggest to go a little bit deeper and validate more configuration options > and add validation for JVM and OS settings. > Ignite should output warning if: > * GC logging is not enabled > * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize) > * Heap size is greater than 30,5G and JVM cannot use compressed oops > * Any of the recommended OS setting described here > https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly > set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[ https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814243#comment-15814243 ] Vyacheslav Daradur edited comment on IGNITE-4374 at 1/10/17 8:03 AM: - [^x64_not_optimized.png] [^x64_optimized.png] [^x32_not_optimized.png] [^x32_optimized.png] '-server' option checks only on not x64 VM bq. On a 64-bit capable JDK, only the Java Hotspot Server VM is supported so the -server option is implicit http://docs.oracle.com/javase/7/docs/technotes/guides/vm/server-class.html was (Author: daradurvs): x64 - not optimized [^x64_not_optimized.png] x64 - optimized !x64_optimized.png|thumbnail! x32 - not optimized !x32_not_optimized.png|thumbnail! x32 - optimized !x32_optimized.png|thumbnail! '-server' option checks only on not x64 VM bq. On a 64-bit capable JDK, only the Java Hotspot Server VM is supported so the -server option is implicit http://docs.oracle.com/javase/7/docs/technotes/guides/vm/server-class.html > Ignite should validate JVM and OS configuration and output warning in log > - > > Key: IGNITE-4374 > URL: https://issues.apache.org/jira/browse/IGNITE-4374 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Yakov Zhdanov >Assignee: Vyacheslav Daradur > Attachments: check-output.png, x32_not_optimazed.png, > x32_optimazed.png, x64_not_optimized.png, x64_optimized.png > > > Currently we have GridPerformanceSuggestions that output suggestions to logs > on Ignite start on how Ignite can be improved. > I suggest to go a little bit deeper and validate more configuration options > and add validation for JVM and OS settings. > Ignite should output warning if: > * GC logging is not enabled > * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize) > * Heap size is greater than 30,5G and JVM cannot use compressed oops > * Any of the recommended OS setting described here > https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly > set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[ https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814243#comment-15814243 ] Vyacheslav Daradur edited comment on IGNITE-4374 at 1/10/17 7:55 AM: - x64 - not optimized [^x64_not_optimized.png] x64 - optimized !x64_optimized.png|thumbnail! x32 - not optimized !x32_not_optimized.png|thumbnail! x32 - optimized !x32_optimized.png|thumbnail! '-server' option checks only on not x64 VM bq. On a 64-bit capable JDK, only the Java Hotspot Server VM is supported so the -server option is implicit http://docs.oracle.com/javase/7/docs/technotes/guides/vm/server-class.html was (Author: daradurvs): x64 - not optimized !x64_not_optimized.png|thumbnail! x64 - optimized !x64_optimized.png|thumbnail! x32 - not optimized !x32_not_optimized.png|thumbnail! x32 - optimized !x32_optimized.png|thumbnail! '-server' option checks only on not x64 VM bq. On a 64-bit capable JDK, only the Java Hotspot Server VM is supported so the -server option is implicit http://docs.oracle.com/javase/7/docs/technotes/guides/vm/server-class.html > Ignite should validate JVM and OS configuration and output warning in log > - > > Key: IGNITE-4374 > URL: https://issues.apache.org/jira/browse/IGNITE-4374 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Yakov Zhdanov >Assignee: Vyacheslav Daradur > Attachments: check-output.png, x32_not_optimazed.png, > x32_optimazed.png, x64_not_optimized.png, x64_optimized.png > > > Currently we have GridPerformanceSuggestions that output suggestions to logs > on Ignite start on how Ignite can be improved. > I suggest to go a little bit deeper and validate more configuration options > and add validation for JVM and OS settings. > Ignite should output warning if: > * GC logging is not enabled > * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize) > * Heap size is greater than 30,5G and JVM cannot use compressed oops > * Any of the recommended OS setting described here > https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly > set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log
[
https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812261#comment-15812261
]
Vyacheslav Daradur edited comment on IGNITE-4374 at 1/9/17 5:09 PM:
Check of "Basic JVM Configuration" added.
Options are checked:
{code}
-server
-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
{code}
Link to the tuning article added to output.
!https://issues.apache.org/jira/secure/attachment/12846372/check-output.png|thumbnail!
If the community approves this approach I will develop checks for ON_HEAP and
OFF_HEAP "Advanced JVM Configuration"
was (Author: daradurvs):
Check of "Basic JVM Configuration" added.
Options are checked:
{code}
-server
-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
{code}
Link to the tuning article added to output.
!check-output.png|thumbnail!
If the community approves this approach I will develop checks for ON_HEAP and
OFF_HEAP "Advanced JVM Configuration"
> Ignite should validate JVM and OS configuration and output warning in log
> -
>
> Key: IGNITE-4374
> URL: https://issues.apache.org/jira/browse/IGNITE-4374
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Yakov Zhdanov
>Assignee: Vyacheslav Daradur
> Attachments: check-output.png
>
>
> Currently we have GridPerformanceSuggestions that output suggestions to logs
> on Ignite start on how Ignite can be improved.
> I suggest to go a little bit deeper and validate more configuration options
> and add validation for JVM and OS settings.
> Ignite should output warning if:
> * GC logging is not enabled
> * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
> * Heap size is greater than 30,5G and JVM cannot use compressed oops
> * Any of the recommended OS setting described here
> https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly
> set
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
