Hi: I in a very old machine simple to do the test, if open reserv mechanism, the ID generation speed can reach 50K/s. If turn off reserv mechanism, the performance will be dropped to 13K/s, performance degradation is very obvious, but off reserv will enable ID increase linearly with time, this aspect of the advantages and disadvantages can allow developers to choose their own.
In addition, the performance of IgniteAtomicSequence may related to the performance of cache nodes, therefore,AtomicConfiguration, whether it is necessary to add an attribute, similar nodeFilter such, let developers control a distributed datastructure cache deployed on the nodes with high performance. Sent from Mail Master On 2016-01-20 04:29 , Dmitriy Setrakyan Wrote: The performance of AtomicSequence is very good as most of the operations are local. The way it works is that it will reserve a range of numbers by sending a request, but then will return all new IDs locally, until the reserved range is exhausted. More information here: https://apacheignite.readme.io/docs/id-generator D. On Tue, Jan 19, 2016 at 4:54 AM, 李玉珏@163 <18624049...@163.com> wrote: > Hi： > > Oh, sorry, wrong title. > > 在 16/1/19 16:50, Dmitriy Setrakyan 写道: > >> Yujue Li, what exactly would you like to benchmark? Is it the >> IgniteAtomicSequence or IgniteAtomicReference? Also, benchmarks are better >> viewed in comparison to something else. Is there something else in >> particular you would like to compare these data structures to? >> >> D. >> >> On Sun, Jan 17, 2016 at 7:31 PM, 李玉珏 <18624049...@163.com> wrote: >> >> Hi: >>> >>> About IgniteAtomicReference, I think the function in the existing >>> distributed ID generator advantage is very obvious, if converted to >>> hexadecimal, can do a very short。 >>> >>> I would like to ask, is there a particular description about the >>> performance? Did the benchmark test on a specific hardware? >>> >> > >
