the implement of primaryEntrySet() in ignite 1.6 is this:

<http://apache-ignite-users.70518.x6.nabble.com/file/n6171/QQ%E6%88%AA%E5%9B%BE20160708165043.png>
 

this function may *scan all the partitions including backup partitions* on
local node, then filter each entry with this CacheEntryPredicate:

<http://apache-ignite-users.70518.x6.nabble.com/file/n6171/QQ%E6%88%AA%E5%9B%BE20160708165637.png>
 

I think it has poor performance. 

Since we can get the primary partitions id of localnode from
GridAffinityAssignment:

<http://apache-ignite-users.70518.x6.nabble.com/file/n6171/QQ%E6%88%AA%E5%9B%BE20160708170536.png>
 

why not get primary partitions directly(not including backup partitions) and
then return all the entry of primary partitions(no need use
CacheEntryPredicate to judge each entry)?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/performance-on-the-function-primaryEntrySet-tp6171.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to