3. if this is cache message and its target partition is determined it goes to particular stripe (put requests, lock requests, etc)
If partition is not determined cache message goes to random stripe (update response, prepare request, commit request, etc) - btw this needs to be fixed and we need to spread partition info to these messages where applicable, eg finish txs on per partition basis - this way we eliminate contention on cache entries and partitions. Query requests go to system pool since they may iterate over entire cache. For some messages we still need to use sys pool - sometimes Ignite fallbacks to sync waiting in internal threads. This is obviously an issue that needs to be fixed. I have list of such places to fix. --Yakov
