[
https://issues.apache.org/jira/browse/IMPALA-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17580449#comment-17580449
]
Michael Smith edited comment on IMPALA-10214 at 8/16/22 11:07 PM:
------------------------------------------------------------------
Started some perf test runs to compare Ozone and HDFS performance:
* https://jenkins.impala.io/job/perf-AB-test/349/ compares Ozone without file
caching to HDFS
* https://jenkins.impala.io/job/perf-AB-test/350/ compares Ozone with file
caching to Ozone without file caching
Update: didn't work because they expect to be able to use Hive to load data.
I'll have to look at how to bypass that and do similar runs locally.
was (Author: JIRAUSER288956):
Started some perf test runs to compare Ozone and HDFS performance:
* https://jenkins.impala.io/job/perf-AB-test/349/ compares Ozone without file
caching to HDFS
* https://jenkins.impala.io/job/perf-AB-test/350/ compares Ozone with file
caching to Ozone without file caching
> Ozone support for file handle cache
> -----------------------------------
>
> Key: IMPALA-10214
> URL: https://issues.apache.org/jira/browse/IMPALA-10214
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Reporter: Sahil Takiar
> Assignee: Michael Smith
> Priority: Major
>
> This is dependent on the Ozone input streams supporting the {{CanUnbuffer}}
> interface first (last I checked, the input streams don't implement the
> interface).
> There should be a flag that enables/disables file handle caching for Ozone
> for both local and remote access. Default to disabled. Address IMPALA-10375
> while updating this logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
