Hi,
As for CPUs, I still don't see why do you need this. These CPUs are not > "allocated" by an Ignite node, they are just available to it. So if there > is > enough CPU time for both Ignite and your application which share one box, > it > will work. In other words, let operating system properly manage the > resources. > I think what counts is the number of jobs/tasks which can be executed by one node at a given time. I think this should be configurable within ignite. Here's my use case. We want to run a distributed computation using a third-party tool which, when executed, takes an entire CPU core. We'll wrap that execution in Java in an Ignite task/job (sorry, I alwas forget which is which). On a multi-core machines we'd like to be able to run N-X tasks simultaneously where N is a number of cores and X is 1 or 2 (for 4-core or >8-core machines) reserved for administrative/management tasks. Like, 14 cores for a 16-core machine. At the moment my understanding is that we'll need to start N-X nodes per server, to handle N-X jobs/tasks at once, correct? Best wishes, Alexey
