Hi Yun I think whether atomic increased number or timestamp, the key point is disperse the elements in the different keys. My point is how to design a useful key. For the atomic increased number, it will array the elements one by one but I think the key is useless. Because the max key is not the elements count, when we implement the remove method. Currently, for the CountEvictor, TimeEvictor and TTL scenario, we should iteration all of the elements to find what we want. But if we use timestamp key, we could terminal the iteration early to save performance or start from the available timestamp to iteration the rest elements.
-- Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
