Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 81DC818DC3 for ; Tue, 19 Jan 2016 12:26:11 +0000 (UTC) Received: (qmail 54289 invoked by uid 500); 19 Jan 2016 12:26:11 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 54246 invoked by uid 500); 19 Jan 2016 12:26:11 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 54234 invoked by uid 99); 19 Jan 2016 12:26:10 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2016 12:26:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 07180180626 for ; Tue, 19 Jan 2016 12:26:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.607 X-Spam-Level: ** X-Spam-Status: No, score=2.607 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FROM_LOCAL_DIGITS=0.001, FROM_LOCAL_HEX=0.331, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_PSBL=2.7, RP_MATCHES_RCVD=-0.554, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=163.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id t64kU3ljPV-o for ; Tue, 19 Jan 2016 12:26:09 +0000 (UTC) Received: from m50-138.163.com (m50-138.163.com [123.125.50.138]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTP id 8364520CB8 for ; Tue, 19 Jan 2016 12:26:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Subject:From:Message-ID:Date:MIME-Version; bh=x4Mld ZXf5XjczUfsoMWs5TEAu+hK5aKu6qTVDXwmYVQ=; b=CR2RegCIU0VUErcZ9vEhq evWAzI7WQ6d3dQLDBNOT3puqfH/d0i4r52VjgC5QO5ae2TzfjGfIkqYA87vCqhCv S0WVuYhvDTmY55W3WuY6ZzlCDh79WRqj2nD4zFrzEPWKCfpzG9KNLLXYypIb7ntF KX5LkuS5BtQoNDJYso/7Rs= Received: from liyujuematoMacBook-Air.local (unknown [175.168.203.99]) by smtp1 (Coremail) with SMTP id C9GowABHTGxRK55Wh35nAg--.4003S2; Tue, 19 Jan 2016 20:25:54 +0800 (CST) Subject: Re: About IgniteAtomicReference To: dev@ignite.apache.org References: <5b9430d6.4f6f.1525292baa9.Coremail.18624049226@163.com> From: =?UTF-8?B?5p2O546J54+PQDE2Mw==?= <18624049226@163.com> Message-ID: <569E2B63.9030804@163.com> Date: Tue, 19 Jan 2016 20:26:11 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-CM-TRANSID: C9GowABHTGxRK55Wh35nAg--.4003S2 X-Coremail-Antispam: 1Uf129KBjvJXoW7tFyUZFyxKF4fGFWxXrWkZwb_yoW8Ww4kpF WqkFyDtF4DXF4rJayava1xXFya9r9aqrW5JryrGr17Jw45WrZFqr42kw1S9FZ09rnrK3Wj vF4I9a4UCa9Yk3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x07jsUUUUUUUU= X-Originating-IP: [175.168.203.99] X-CM-SenderInfo: pvdktzbdstjqqrwthudrp/1tbiGBP0jVXlSQHTZwAAs+ Hi: I am concerned about the IgniteAtomicSequence, which function is distributed ID generator, so the performance is very important. I don't think IgniteAtomicReference has a performance problem. The solution of the distributed ID generator is very much, the technical route is different, applicable scene is also different, the simple comparison of performance is not significant. I think to refer to the developers, the official gives a specific hardware performance data can be, the remaining let developers themselves to make a choice, such as: 4*core 2.4GHz, 16g memory,no reserve, every second can generate 10000 ID. 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. Thanks! 在 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, 李玉珏 <18624049226@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?