Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5A631200B58 for ; Wed, 27 Jul 2016 19:10:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 59345160A90; Wed, 27 Jul 2016 17:10:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 764D5160A6F for ; Wed, 27 Jul 2016 19:10:46 +0200 (CEST) Received: (qmail 14378 invoked by uid 500); 27 Jul 2016 17:10:45 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 14366 invoked by uid 99); 27 Jul 2016 17:10:45 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jul 2016 17:10:45 +0000 Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 2BAA61A00C5 for ; Wed, 27 Jul 2016 17:10:45 +0000 (UTC) Received: by mail-wm0-f53.google.com with SMTP id q128so220888003wma.1 for ; Wed, 27 Jul 2016 10:10:45 -0700 (PDT) X-Gm-Message-State: AEkoouvPmW1odrzBzhyQnSHU2vw8hjTpJ2KJIXGDaQpZOh9CWAIRzk0Q904v0wn8v9ixL9qCPXbDnwa7HlIU6gLN X-Received: by 10.28.19.134 with SMTP id 128mr32882002wmt.40.1469639443789; Wed, 27 Jul 2016 10:10:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.203.134 with HTTP; Wed, 27 Jul 2016 10:09:54 -0700 (PDT) In-Reply-To: References: <1468852357124-6345.post@n6.nabble.com> <1469014976182-6419.post@n6.nabble.com> From: Dmitriy Setrakyan Date: Wed, 27 Jul 2016 13:09:54 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Hazelcast vs Ignite vs Geode To: user Content-Type: multipart/alternative; boundary=001a11467774ff108b0538a1188c archived-at: Wed, 27 Jul 2016 17:10:47 -0000 --001a11467774ff108b0538a1188c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Jul 27, 2016 at 9:58 AM, Ralph Goers wrote: > That is not strictly correct. You can do objective performance testing o= f > Ignite and compare that to other solutions, where it is allowed (which it > typically would be for other open source solutions). When you do this, it > should be done in a way that helps users understand how to best configure > Ignite. For example, show how the results differ with different > configuration values and in different use cases. > If that's the case, I would run the benchmarks again with completely clear Ignite configuration in github and a proper description on it. I really miss the benchmark results personally, they added a lot of clarity about how to run and configure the project for performance. > > Ralph > > On Jul 21, 2016, at 12:55 PM, Dmitriy Setrakyan > wrote: > > I would like to add that Ignite community as part of the Apache Software > Foundation cannot publish any competitive benchmarks or product > comparisons. This is the reason why we generally provide links to externa= l > resources for questions like this. > > On Wed, Jul 20, 2016 at 4:42 AM, Denis Magda wrote: > >> Hi, >> >> Please properly subscribe to the user list so that we can see your >> questions >> as soon as possible and provide answers on them quicker. All you need to >> do >> is send an email to user-subscribe@ignite.apache.org=C3=AE and follow si= mple >> instructions in the reply. >> >> >> Reddy wrote >> > Hi All, >> > >> > We want to know the best features of Apache ignite(GridGain) when >> compared >> > to other In memory databases(Hazelcast,Geode) with respective of >> > performnace,reads,writes,backup,storage and keys metadata etc. >> > Why I am asking this question that you people have solid understanding >> of >> > ignite and already might have compared with other IMDBs. >> > >> > Pls let me know if you have any metrics also. >> >> I would suggest you referring to GridGain's products comparison page [1] >> and >> benchmarks page [2] which have extensive information on what you're >> looking >> for. >> >> [1] http://www.gridgain.com/resources/product-comparisons >> [2] http://www.gridgain.com/resources/benchmarks >> >> -- >> Denis >> >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/Hazelcast-vs-Ignite-vs-Ge= ode-tp6345p6419.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com >> . >> > > > --001a11467774ff108b0538a1188c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Jul 27, 2016 at 9:58 AM, Ralph Goers <ralph.goers@dsl= extreme.com> wrote:
That is not strictly correct.=C2=A0 You c= an do objective performance testing of Ignite and compare that to other sol= utions, where it is allowed (which it typically would be for other open sou= rce solutions). When you do this, it should be done in a way that helps use= rs understand how to best configure Ignite. For example, show how the resul= ts differ with different configuration values and in different use cases.

If that's the case, I would = run the benchmarks again with completely clear Ignite configuration in gith= ub and a proper description on it. I really miss the benchmark results pers= onally, they added a lot of clarity about how to run and configure the proj= ect for performance.
=C2=A0
<= div style=3D"word-wrap:break-word">

Ralph
=
On Jul 21, 2016, at 12:55 PM, Dmitr= iy Setrakyan <dsetrakyan@apache.org> wrote:

I woul= d like to add that Ignite community as part of the Apache Software Foundati= on cannot publish any competitive benchmarks or product comparisons. This i= s the reason why we generally provide links to external resources for quest= ions like this.

On= Wed, Jul 20, 2016 at 4:42 AM, Denis Magda <dmagda@gridgain.com><= /span> wrote:
Hi,

Please properly subscribe to the user list so that we can see your question= s
as soon as possible and provide answers on them quicker. All you need to do=
is send an email to user-subscribe@ignite.apache.org=C3=AE and follow simpl= e
instructions in the reply.


Reddy wrote
> Hi All,
>
> We want to know the best features of Apache ignite(GridGain) when comp= ared
> to other In memory databases(Hazelcast,Geode) with respective of
> performnace,reads,writes,backup,storage and keys metadata etc.
> Why I am asking this question that you people have solid understanding= of
> ignite and already might=C2=A0 have compared with other IMDBs.
>
> Pls let me know if you have any metrics also.

I would suggest you referring to GridGain's products comparison page [1= ] and
benchmarks page [2] which have extensive information on what you're loo= king
for.

[1] http://www.gridgain.com/resources/product= -comparisons
[2] http://www.gridgain.com/resources/benchmarks

--
Denis




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Hazelc= ast-vs-Ignite-vs-Geode-tp6345p6419.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.



--001a11467774ff108b0538a1188c--