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 2CB41200C5D for ; Fri, 24 Mar 2017 07:06:56 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 2B376160B84; Fri, 24 Mar 2017 06:06:56 +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 739E0160B83 for ; Fri, 24 Mar 2017 07:06:55 +0100 (CET) Received: (qmail 28080 invoked by uid 500); 24 Mar 2017 06:06:49 -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 28070 invoked by uid 99); 24 Mar 2017 06:06:49 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Mar 2017 06:06:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 1B4951AFB8C for ; Fri, 24 Mar 2017 06:06:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.674 X-Spam-Level: ** X-Spam-Status: No, score=2.674 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, KAM_NUMSUBJECT=0.5, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 9fU65G4yul-g for ; Fri, 24 Mar 2017 06:06:48 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 403CE5FE22 for ; Fri, 24 Mar 2017 06:06:48 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 63C473F921F9 for ; Thu, 23 Mar 2017 22:41:36 -0700 (PDT) Date: Thu, 23 Mar 2017 23:06:46 -0700 (MST) From: zaid To: user@ignite.apache.org Message-ID: <1490335606898-11405.post@n6.nabble.com> In-Reply-To: References: <1488534714911-11013.post@n6.nabble.com> <1488801210274-11035.post@n6.nabble.com> <1488802313716-11036.post@n6.nabble.com> <1489555670266-11176.post@n6.nabble.com> <1489743775051-11268.post@n6.nabble.com> Subject: Re: Very slow cache query compared to H2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Fri, 24 Mar 2017 06:06:56 -0000 Hi, Thanks for your time looking into the issue. I have modified SlowQuery program and now you should get 10 records as query response. SlowQuery.java My concern is that we need to decide whether we should continue using MySQL or switch to Ignite SQL. MySQL takes 56 milliseconds to execute the query whereas SQL grid takes 7220 milliseconds in client server mode for my use case. Are there any optimizations I can do to reduce Ignite SQL execution time with respect to configuration? Regards, Zaid -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Very-slow-cache-query-compared-to-H2-tp11013p11405.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.