Return-Path: X-Original-To: apmail-atlas-dev-archive@minotaur.apache.org Delivered-To: apmail-atlas-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BA6641898B for ; Tue, 1 Dec 2015 17:05:14 +0000 (UTC) Received: (qmail 64362 invoked by uid 500); 1 Dec 2015 17:05:14 -0000 Delivered-To: apmail-atlas-dev-archive@atlas.apache.org Received: (qmail 64323 invoked by uid 500); 1 Dec 2015 17:05:14 -0000 Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@atlas.incubator.apache.org Delivered-To: mailing list dev@atlas.incubator.apache.org Received: (qmail 64312 invoked by uid 99); 1 Dec 2015 17:05:14 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2015 17:05:14 +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 300D418098E for ; Tue, 1 Dec 2015 17:05:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.226 X-Spam-Level: * X-Spam-Status: No, score=1.226 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.554] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id nHVhNlBCU-Es for ; Tue, 1 Dec 2015 17:05:12 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id B9C5020CFA for ; Tue, 1 Dec 2015 17:05:12 +0000 (UTC) Received: (qmail 63950 invoked by uid 99); 1 Dec 2015 17:05:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2015 17:05:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1B5A82C1F75 for ; Tue, 1 Dec 2015 17:05:11 +0000 (UTC) Date: Tue, 1 Dec 2015 17:05:11 +0000 (UTC) From: "Suma Shivaprasad (JIRA)" To: dev@atlas.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ATLAS-352) Fix performance issues with type and entity creation with Hbase as storage backend MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ATLAS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034074#comment-15034074 ] Suma Shivaprasad commented on ATLAS-352: ---------------------------------------- On investigating, it was found that Titan holds locks at 2 levels - one at a local level among threads and another at a global level as a distributed lock among titan instances. The disrtibuted lock is maintained for every KeyColumn that its trying to mutate in Hbase and it ends up doing a lot of writes for locking and lot of reads to check if the current local original values before the mutation began for the keyColumn are matching with the ones during transaction commit. If it doesnt match, the transaction is failed. As for Atlas , since it operates only a single instance of Titan currently, the locks can be maintained only at a local level among different threads in the same JVM(Atlas) > Fix performance issues with type and entity creation with Hbase as storage backend > ----------------------------------------------------------------------------------- > > Key: ATLAS-352 > URL: https://issues.apache.org/jira/browse/ATLAS-352 > Project: Atlas > Issue Type: Improvement > Affects Versions: 0.6-incubating > Reporter: Suma Shivaprasad > Assignee: Suma Shivaprasad > > Current perf microbenchmark measurements > DataSet quickstart model and entity definitions > No of class types 6 > traits 6 with no attributes > server start up time with existing schema 17 secs > type batch creation 27 secs > entity creation - DB 12 secs > entity creation - Table 11 secs -- This message was sent by Atlassian JIRA (v6.3.4#6332)