[
https://issues.apache.org/jira/browse/COMPRESS-540?focusedWorklogId=515258&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-515258
]
ASF GitHub Bot logged work on COMPRESS-540:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Nov/20 13:15
Start Date: 22/Nov/20 13:15
Worklog Time Spent: 10m
Work Description: theobisproject commented on pull request #113:
URL: https://github.com/apache/commons-compress/pull/113#issuecomment-731746841
> `readLastEntry_tarStream` is even slower than eithor
My guess would be that the performance characteristic of `IOUtils.skip` is
quite different than the writing to the `NullOutputStream` in the benchmark.
If someone is only interested in the overhead of the `TarFile`
implementation this benchmark can be added.
```java
@Benchmark
public void tarFileOverhead() throws IOException {
try (TarFile tarFile = new TarFile(getLargeTarPath())) {
// Do nothing to only measure the overhead of reading all files
header information
}
}
```
----------------------------------------------------------------
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: 515258)
Time Spent: 4h 50m (was: 4h 40m)
> Random access on Tar archive
> ----------------------------
>
> Key: COMPRESS-540
> URL: https://issues.apache.org/jira/browse/COMPRESS-540
> Project: Commons Compress
> Issue Type: Improvement
> Reporter: Robin Schimpf
> Priority: Major
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> The TarArchiveInputStream only provides sequential access. If only a small
> amount of files from the archive is needed large amount of data in the input
> stream needs to be skipped.
> Therefore I was working on a implementation to provide random access to
> TarFiles equal to the ZipFile api. The basic idea behind the implementation
> is the following
> * Random access is backed by a SeekableByteChannel
> * Read all headers of the tar file and save the place to the data of every
> header
> * User can request an input stream for any entry in the archive multiple
> times
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
