From user-return-26256-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Jun 14 13:49:58 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7D9D518062F for ; Fri, 14 Jun 2019 15:49:58 +0200 (CEST) Received: (qmail 96411 invoked by uid 500); 14 Jun 2019 13:49:56 -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 96401 invoked by uid 99); 14 Jun 2019 13:49:56 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jun 2019 13:49:56 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 5D77EC2998 for ; Fri, 14 Jun 2019 13:49:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.899 X-Spam-Level: X-Spam-Status: No, score=-0.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=isnil.de Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id o2Wz2WMt2oGH for ; Fri, 14 Jun 2019 13:49:53 +0000 (UTC) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.161]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 366375F490 for ; Fri, 14 Jun 2019 13:49:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1560520187; s=strato-dkim-0002; d=isnil.de; h=Date:Message-ID:To:Subject:From:X-RZG-CLASS-ID:X-RZG-AUTH:From: Subject:Sender; bh=BCyGOZPvWqI6OXyiQPdECKWa1rNKM88r+TE2A2sA3CA=; b=rHZb3Q6FkWcRjkKNFvljG9gy2WQRnQTpoYGbZkcfKp2OZBFfpTx5kEmj4G/RTZTUNB RtxBlMJjCI/qfsixnLJyTa2hTfOExRHmRb2f/NfqNUBFOrOxI+griZowAvkuqksQV0Fc QQsOm/+GuMPstoPup+zH/jS77NQU5SNr6CSyRXR/j0oaLEfbmTVkuaBvZsQfG9j1qlIn 68Vq8SnRfb1rl3LKYtRnuU+d1B/4oLB5safmumxsPwmnAj0x1oTgDQQMzdr372KzIIWn 4me47T5hiu4QWzszV3sI4XXe7pR9V8lbD1hv651kWFgf18vibr+GpN6HZpDU9YtuS1jD ZdaQ== X-RZG-AUTH: ":P2MCYVepafr3Bjk5dD7K61SKOowJrz1VxYzfx2VSh6sucS5iPCvMJBI+y2pEaTJ5KpPkbnMrJVFGIyCQrxXI0s7lnMXjd2HZ9LM=" X-RZG-CLASS-ID: mo00 Received: from [IPv6:2003:c6:ef17:3c00:f9af:e76a:99e:93e0] by smtp.strato.de (RZmta 44.23 AUTH) with ESMTPSA id Q03d42v5EDnl7iP (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Fri, 14 Jun 2019 15:49:47 +0200 (CEST) From: Dieter Guthardt Subject: Ignite client - slow startup To: user@ignite.apache.org Message-ID: Date: Fri, 14 Jun 2019 15:49:47 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Hi, we're currently running a couple of servers with various Ignite scenarios - version 2.6 and 2.7. With and without persistence and some only get used to perform server based computations without any cache. It's quite satisfying except the startup time of the client applications is pretty slow especially running them from 'remote'. I realized depending on the cluster configuration the topology send around when connecting can get huge. Even the clusters without caches get really big and it's time consuming to connect. That's all related to the snapshot version, so higher the number so bigger the amount of data transferred and slower the connection. The client instance of Ignite gets bigger and bigger depending on the cluster, cache and snapshot history. Since I haven't found a satisfying answer yet I started digging into your code and found the following: In the class TcpDiscoverySpi you set the default history size of the discoCache to be 1000! After reducing the number to 10 I obtained a decent startup time. Debugging the ignite client instance now shows a constant size after reaching a snapshot version > 10. I was wondering why the history was set to 1000? How does a small number affect the cluster? Br, Will