The question is what is happening when I call `.withAsync()` and then call any of the method of the returned `IgniteAsyncSupport`? Will Ignite run the requested operation in the new thread? Does it use Java Executor underneath? Or just manages its own thread pool? Is it possible to configure how threads behind async work (i.e. number of threads, pool size, etc.)?
What if I have to put the item in the cache a few every second? Will `IgniteAsyncSupport` handle it gracefully? (also for that specific cache I configure the expiry policy of a 5 minutes and write through enabled with write behind flush frequency of 1 minute). So, the idea behind this cache is do not block my current thread while persisting the data, and delegate this to the cache itself (by enabling write through) (I also actually use a cache, and I am interested/need only a few minutes of data to be in the cache in order to proceed with the business logic, this is why the expiry policy is 5 minutes). On a side note, are there other ways to solve the described problem above using Ignite (other Ignite features)? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-Asynchronous-support-works-underneath-5-10-put-calls-every-second-tp6482.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
