Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 2 Feb 2016 06:30:39 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12935863.1454394268000.273563.1454394639798@Atlassian.JIRA>
In-Reply-To: <JIRA.12935863.1454394268000@Atlassian.JIRA>
References: <JIRA.12935863.1454394268000@Atlassian.JIRA>
 <JIRA.12935863.1454394268979@arcas>
Subject: [jira] [Updated] (HBASE-15203) Reduce garbage created by
 path.toString() during Checksum verification
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-15203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ramkrishna.s.vasudevan updated HBASE-15203:
-------------------------------------------
    Attachment: HBASE-15203.patch

Simple patch which caches the pathName on the FSReaderImpl creation.

> Reduce garbage created by path.toString() during Checksum verification
> ----------------------------------------------------------------------
>
>                 Key: HBASE-15203
>                 URL: https://issues.apache.org/jira/browse/HBASE-15203
>             Project: HBase
>          Issue Type: Sub-task
>          Components: regionserver
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15203.patch
>
>
> When we try to read a block we do checksum verification for which we need the file name in which the block belongs to. So we do Path.toString() every time. This seems to create around 163MB of char[] that is garbage collected in a simple scan run. It is also visible in writes but the impact is lesser. In overall write/read profile the top 2 factors are byte[] and char[]. This toString() can easily be avoided and reduce its share from the total. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)