[
https://issues.apache.org/jira/browse/COMPRESS-623?focusedWorklogId=800259&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-800259
]
ASF GitHub Bot logged work on COMPRESS-623:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Aug/22 10:18
Start Date: 12/Aug/22 10:18
Worklog Time Spent: 10m
Work Description: dweiss commented on PR #306:
URL: https://github.com/apache/commons-compress/pull/306#issuecomment-1212955649
Eh. It wasn't me - it was intellij for some reason... That's why I like
spotless/google formatter... makes life much easier for folks using different
tools. Give me a minute to revert those changes.
Issue Time Tracking
-------------------
Worklog Id: (was: 800259)
Time Spent: 0.5h (was: 20m)
> Speed up ZipFile's raw stream copying by not seeking for local headers until
> they're needed
> -------------------------------------------------------------------------------------------
>
> Key: COMPRESS-623
> URL: https://issues.apache.org/jira/browse/COMPRESS-623
> Project: Commons Compress
> Issue Type: Improvement
> Reporter: Dawid Weiss
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I have a somewhat odd use case with gigabytes of ZIP files, each with
> thousands of documents (on comparatively slow, network drives). We need to
> restructure these ZIPs without the need to recompress files.
> The above turns out to work almost perfectly with raw-data copying ZipFile
> offers but empirical tests showed a major slowdown in the initial opening of
> zip files, linked to multiple reads/seeks for local file headers. If an
> option is passed to ignore those headers, raw streams are inaccessible.
> I've taken a look at the code and the code in getRawInputStream could
> basically do the same thing that getInputStream does - lazily load the
> missing offset via getDataOffset(ZipEntry). In fact, getInputStream could
> just call getRawInputStream directly, which avoids some code duplication.
> I also restructured the code that maintains LinkedList for duplicated names a
> bit. I think this bit could be removed altogether and replaced with a
> pointer-chain list directly on Entry class instances (the map would then
> point at the first entry; duplicated entries are an oddity and infrequent in
> the wild).
> I see speedups for opening and copying random raw streams in the order of
> 3-4x and all the current tests pass. I filed a PR at github - happy to
> discuss it there.
> https://github.com/apache/commons-compress/pull/306
--
This message was sent by Atlassian Jira
(v8.20.10#820010)