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 542E7200B4F for ; Tue, 26 Jul 2016 21:01:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 52CB9160AA4; Tue, 26 Jul 2016 19:01:15 +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 C0438160AA2 for ; Tue, 26 Jul 2016 21:01:14 +0200 (CEST) Received: (qmail 97356 invoked by uid 500); 26 Jul 2016 19:01:13 -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 97346 invoked by uid 99); 26 Jul 2016 19:01:13 -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; Tue, 26 Jul 2016 19:01:13 +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 874A51A0454 for ; Tue, 26 Jul 2016 19:01:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 1b6utHE4xxqi for ; Tue, 26 Jul 2016 19:01:11 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 0FEDC5F295 for ; Tue, 26 Jul 2016 19:01:11 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 7231B2D57438 for ; Tue, 26 Jul 2016 11:37:04 -0700 (PDT) Date: Tue, 26 Jul 2016 11:43:48 -0700 (PDT) From: vkulichenko To: user@ignite.apache.org Message-ID: <1469558628708-6549.post@n6.nabble.com> In-Reply-To: <1469523445269-6539.post@n6.nabble.com> References: <1469217680526-6482.post@n6.nabble.com> <1469487918889-6526.post@n6.nabble.com> <1469523445269-6539.post@n6.nabble.com> Subject: Re: How Asynchronous support works underneath? 60 * N put calls every second MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 26 Jul 2016 19:01:15 -0000 Ignite uses async IO for communication. So it just asynchronously send a request message and creates a future which will be completed when response for this request is received. So there is nothing actually happening while we're waiting for response and another thread is not needed. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-Asynchronous-support-works-underneath-60-N-put-calls-every-second-tp6482p6549.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.