[
https://issues.apache.org/jira/browse/HDDS-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913586#comment-16913586
]
Anu Engineer edited comment on HDDS-1094 at 8/22/19 8:14 PM:
-------------------------------------------------------------
{quote}yes, I understand. exactly why I said earlier, depends on what we wish
to test.
{quote}
What is the test that we can do? We can write to a fast storage system, but we
can never read back? So how do we even know that that we exercised any path?
Would it not make more sense to be able to exercise Metadata and Data paths
separately ?
Really I am having difficulty in trying to understand what scenarios are
enabled by this patch to justify to support this is as feature.
was (Author: anu):
{quote}yes, I understand. exactly why I said earlier, depends on what we wish
to test.
{quote}
What is the test that we can do? We can write to a fast storage system, but we
can never read back? So how do we even know that that we exercised any path?
Would it not make more sense to be able to exercise Metadata and Data paths
separately ?
Really I am difficulty trying to understand what scenarios are enabled by this
patch to justify to support this is as feature.
> Performance test infrastructure : skip writing user data on 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
> Assignee: Supratim Deka
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
