[
https://issues.apache.org/jira/browse/HDDS-1094?focusedWorklogId=299163&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-299163
]
ASF GitHub Bot logged work on HDDS-1094:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Aug/19 04:47
Start Date: 22/Aug/19 04:47
Worklog Time Spent: 10m
Work Description: arp7 commented on pull request #1323: HDDS-1094.
Performance test infrastructure : skip writing user data on Datanode.
Contributed by Supratim Deka
URL: https://github.com/apache/hadoop/pull/1323#discussion_r316494881
##########
File path:
hadoop-ozone/tools/src/main/java/org/apache/hadoop/ozone/freon/RandomKeyGenerator.java
##########
@@ -251,6 +252,12 @@ public void init(OzoneConfiguration configuration) throws
IOException {
@Override
public Void call() throws Exception {
if (ozoneConfiguration != null) {
+ if
(ozoneConfiguration.getBoolean(HddsConfigKeys.HDDS_CONTAINER_PERSISTDATA,
Review comment:
Is this required because you are added a test for freon with the null
ChunkManager?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 299163)
Time Spent: 1h 10m (was: 1h)
> 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 10m
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
