From hdfs-issues-return-273570-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Jul 24 19:34:02 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 34C2B18025F for ; Wed, 24 Jul 2019 21:34:02 +0200 (CEST) Received: (qmail 22871 invoked by uid 500); 24 Jul 2019 19:34:01 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 22850 invoked by uid 99); 24 Jul 2019 19:34:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2019 19:34:01 +0000 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 BBABFE1025 for ; Wed, 24 Jul 2019 19:34:00 +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 7557D265DE for ; Wed, 24 Jul 2019 19:34:00 +0000 (UTC) Date: Wed, 24 Jul 2019 19:34:00 +0000 (UTC) From: "Eric Yang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDDS-1094) Performance testing infrastructure : Special handling for zero-filled chunks on the Datanode 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/HDDS-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892115#comment-16892115 ] Eric Yang commented on HDDS-1094: --------------------------------- HDDS-1772 implements some tests that fill up datanode disk that might be useful here. > Performance testing infrastructure : Special handling for zero-filled chunks on the Datanode > -------------------------------------------------------------------------------------------- > > Key: HDDS-1094 > URL: https://issues.apache.org/jira/browse/HDDS-1094 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Datanode > Reporter: Supratim Deka > Priority: Major > > Goal: > Make Ozone chunk Read/Write operations CPU/network bound for specially constructed performance micro benchmarks. > Remove disk bandwidth and latency constraints - running ozone data path against extreme low-latency & high throughput storage will expose performance bottlenecks in the flow. But low-latency storage(NVME flash drives, Storage class memory etc) is expensive and availability is limited. Is there a workaround which achieves similar running conditions for the software without actually having the low latency storage? At least for specially constructed datasets - for example zero-filled blocks (*not* zero-length blocks). > Required characteristics of the solution: > No changes in Ozone client, OM and SCM. Changes limited to Datanode, Minimal footprint in datanode code. > Possible High level Approach: > The ChunkManager and ChunkUtils can enable writeChunk for zero-filled chunks to be dropped without actually writing to the local filesystem. Similarly, if readChunk can construct a zero-filled buffer without reading from the local filesystem whenever it detects a zero-filled chunk. Specifics of how to detect and record a zero-filled chunk can be discussed on this jira. Also discuss how to control this behaviour and make it available only for internal testing. -- This message was sent by Atlassian JIRA (v7.6.14#76016) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org