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 EF2ED200C78 for ; Thu, 4 May 2017 08:14:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EDB17160BBC; Thu, 4 May 2017 06:14:07 +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 192DE160BB5 for ; Thu, 4 May 2017 08:14:06 +0200 (CEST) Received: (qmail 38140 invoked by uid 500); 4 May 2017 06:14:06 -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 38129 invoked by uid 99); 4 May 2017 06:14:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2017 06:14:06 +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 AC5811883A5 for ; Thu, 4 May 2017 06:14:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.173 X-Spam-Level: **** X-Spam-Status: No, score=4.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, HTML_MESSAGE=2, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id oxev7-9M04Y0 for ; Thu, 4 May 2017 06:14:04 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 36D605F3BB for ; Thu, 4 May 2017 06:14:04 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id BD89D3EDD7E76 for ; Wed, 3 May 2017 23:14:03 -0700 (MST) Date: Wed, 3 May 2017 23:14:03 -0700 (MST) From: afedotov To: user@ignite.apache.org Message-ID: In-Reply-To: <1493858186866-12401.post@n6.nabble.com> References: <1493858186866-12401.post@n6.nabble.com> Subject: Re: Query search performance and scalability MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_263455_1217041725.1493878443762" archived-at: Thu, 04 May 2017 06:14:08 -0000 ------=_Part_263455_1217041725.1493878443762 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable That should be because of the overhead of network roundtrips between the client and the servers. Are servers and client located on the same physical machine? Please provide the query and cache config. Kind regards, Alex 4 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. 3:36 AM =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0= =BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "waterg [via Apache Ignite Users]" = < ml+s70518n12401h65@n6.nabble.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0= =BB: I have a program that issues SQLQuery on colA, colA has a single column index. The cache has about 360K entries, and 298K unique values in colA. I ran the query 1M times with different values. If the cache only has cache key, here's the results I ran with three senario With 1 server node: average search time is 35K nanosecs With 1 server =E2=80=93 1 client: average search time is 128K nanosecs With 2 server =E2=80=93 1 client: average search time is 276K nanosecs If the cache has Affinity Key, here's the results I ran with three senario With 1 server node: average search time is 59K nanosecs With 1 server =E2=80=93 1 client: average search time is 148K nanosecs With 2 server =E2=80=93 1 client: average search time is 287K nanosecs Could anyone advise why the search speed degrades as more nodes are added? Thank you! ------------------------------ If you reply to this email, your message will be added to the discussion below: http://apache-ignite-users.70518.x6.nabble.com/Query-search-performance-and= - scalability-tp12401.html To start a new topic under Apache Ignite Users, email ml+s70518n1h65@n6.nabble.com To unsubscribe from Apache Ignite Users, click here . NAML -- View this message in context: http://apache-ignite-users.70518.x6.nabble.co= m/Query-search-performance-and-scalability-tp12401p12407.html Sent from the Apache Ignite Users mailing list archive at Nabble.com. ------=_Part_263455_1217041725.1493878443762 Content-Type: text/html; charset=UTF8 Content-Transfer-Encoding: quoted-printable
That should be because of the overhead of network roundtrips between the c= lient and the servers. Are servers and client located on the same physical = machine?
Please p= rovide the query and cache config.

Kind re= gards,
Alex

4 =D0=BC=D0=B0=D1=8F 2017 =D0=B3. 3:36 AM =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7= =D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "waterg [via Apache Ignite = Users]" <[hidden email]= > =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
=09
=09=09
If you reply to this email, your mess= age will be added to the discussion below:
=09=09http://apache-ignite-users.70518.x6.nabble.com/Q= uery-search-performance-and-scalability-tp12401.html =09
=09
=09=09To start a new topic under Apache Ignite Users, email [hidden email]
=09=09To unsubscribe from Apache Ignite Users, click here.
=09=09NAML =09

=09 =09 =09
View this message in context: R= e: Query search performance and scalability
Sent from the A= pache Ignite Users mailing list archive at Nabble.com.
------=_Part_263455_1217041725.1493878443762--