[
https://issues.apache.org/jira/browse/PARQUET-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney updated PARQUET-520:
---------------------------------
Description: Repurposed this JIRA after PARQUET-533. Memory-mapping will
save us memory allocations and performance in some applications. We could have
it as an optional API. (was: Noted this while working on PARQUET-497. If we
are using a memory-mapped file, then copying data into a
{{ScopedInMemoryInputStream}} as we are now is unnecessary and will yield
improved performance. Perhaps this should be made a property of the
{{InputStream}} (i.e. indicate whether it support zero-copy reads, and the
returned buffer does not become invalid after future reads as long as the
stream -- the memory map specifically in this example -- is alive))
Summary: Add version of LocalFileSource that uses memory-mapping for
zero-copy reads (was: Add support for zero-copy InputStreams on memory-mapped
files)
> Add version of LocalFileSource that uses memory-mapping for zero-copy reads
> ---------------------------------------------------------------------------
>
> Key: PARQUET-520
> URL: https://issues.apache.org/jira/browse/PARQUET-520
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-cpp
> Reporter: Wes McKinney
> Assignee: Wes McKinney
>
> Repurposed this JIRA after PARQUET-533. Memory-mapping will save us memory
> allocations and performance in some applications. We could have it as an
> optional API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
