You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/01/14 01:31:00 UTC
[jira] [Updated] (ARROW-15332) [C++] Add new cases and fix issues in IPC read/write benchmark
[ https://issues.apache.org/jira/browse/ARROW-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ARROW-15332:
-----------------------------------
Labels: pull-request-available (was: )
> [C++] Add new cases and fix issues in IPC read/write benchmark
> --------------------------------------------------------------
>
> Key: ARROW-15332
> URL: https://issues.apache.org/jira/browse/ARROW-15332
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Weston Pace
> Assignee: Weston Pace
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This breaks out the benchmark changes in ARROW-14577 to allow us to more easily demonstrate the effect of the PR.
> First, there are a few problems with the current benchmark:
> * The benchmark named ReadFile is misleading since it is actually reading from an in-memory buffer and no OS "read" call is ever issued.
> * Renamed ReadTempFile to ReadCachedFile and added a second case for ReadUncachedFile. The former reads a file in the OS' page cache and the latter forces a read to actually hit the disk.
> * The TempFile benchmarks were not actually writing the correct amount of data and were reporting unrealistically high rates as a result.
> * Adding a "partial read" parameter which, when true, only reads 1/8 the columns in the file so we can see the impact of pushdown projection.
> * Slightly reduced the range of parameters to keep the benchmark time reasonable (8k columns wasn't telling us anything more than 4k columns).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)