Hi, Can you please subscribe to the mailing list so that we receive email notification for your posts? You can refer to this instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
Regarding your question. Are you saying that you gonna have only one machine that has an Ignite cache and this machine will be doing all the job described by you below? If so then you can just use a LOCAL cache. I replied you regarding the NPE in the other thread. On the other hand if you're planning to have several machines that will have Ignite cache then I would recommend using either REPLICATED (if cache size is not significant) or PARTITIONED modes. > As my application already using high level of concurrency I need > suggestions to optimize Ignite settings in order to reduce any unnecessary > overhead could be originated from Ignite default settings such as thread > pools for various purposes. Ignite was designed exactly for such environments that are highly distributed and multy-threaded and its default settings work well for 95% projects. I suggest you to start using Ignite with defaults then measure and only the trying to optimize. -- Denis -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Help-required-to-optimize-Ignite-Cache-settings-to-be-used-LOCAL-only-mode-tp1881p1889.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
