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 C9347200C44 for ; Mon, 27 Mar 2017 14:09:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C7A62160B85; Mon, 27 Mar 2017 12:09:45 +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 1972C160B5D for ; Mon, 27 Mar 2017 14:09:44 +0200 (CEST) Received: (qmail 81164 invoked by uid 500); 27 Mar 2017 12:09:44 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 81155 invoked by uid 99); 27 Mar 2017 12:09:44 -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; Mon, 27 Mar 2017 12:09:44 +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 EC3281809E2 for ; Mon, 27 Mar 2017 12:09:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 LyCSCAo1d5pP for ; Mon, 27 Mar 2017 12:09:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0D0EB5FDA9 for ; Mon, 27 Mar 2017 12:09:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4259CE05AE for ; Mon, 27 Mar 2017 12:09:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 985E524067 for ; Mon, 27 Mar 2017 12:09:41 +0000 (UTC) Date: Mon, 27 Mar 2017 12:09:41 +0000 (UTC) From: "Taras Ledkov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (IGNITE-3018) Cache affinity calculation is slow with large nodes number MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 27 Mar 2017 12:09:46 -0000 [ https://issues.apache.org/jira/browse/IGNITE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926181#comment-15926181 ] Taras Ledkov edited comment on IGNITE-3018 at 3/27/17 12:09 PM: ---------------------------------------------------------------- Core review with partitions balancer: [IGNT-CR-137|http://reviews.ignite.apache.org/ignite/review/IGNT-CR-137] was (Author: tledkov-gridgain): Core review with partitions balancer: [IGNT-CR-116|http://reviews.ignite.apache.org/ignite/review/IGNT-CR-116] > Cache affinity calculation is slow with large nodes number > ---------------------------------------------------------- > > Key: IGNITE-3018 > URL: https://issues.apache.org/jira/browse/IGNITE-3018 > Project: Ignite > Issue Type: Bug > Components: cache > Reporter: Semen Boikov > Assignee: Taras Ledkov > Fix For: 2.0 > > Attachments: 003.png, 004.png, 008.png, 016.png, 064.png, 100.png, 128.png, 200.png, 256.png, 400.png, 600.png, balanced.003.png, balanced.004.png, balanced.008.png, balanced.016.png, balanced.064.png, balanced.100.png, balanced.128.png, balanced.200.png, balanced.256.png, balanced.400.png, balanced.600.png > > > With large number of cache server nodes (> 200) RendezvousAffinityFunction and FairAffinityFunction work pretty slow . > For RendezvousAffinityFunction.assignPartitions can take hundredes of milliseconds, for FairAffinityFunction it can take seconds. > For RendezvousAffinityFunction most time is spent in MD5 hash calculation and nodes list sorting. As optimization we can try to cache {partion, node} MD5 hash or try another hash function. Also several minor optimizations are possible (avoid unncecessary allocations, only one thread local 'get', etc). -- This message was sent by Atlassian JIRA (v6.3.15#6346)