[ 
https://issues.apache.org/jira/browse/COMPRESS-540?focusedWorklogId=513896&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-513896
 ]

ASF GitHub Bot logged work on COMPRESS-540:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Nov/20 01:33
            Start Date: 19/Nov/20 01:33
    Worklog Time Spent: 10m 
      Work Description: PeterAlfredLee commented on pull request #113:
URL: https://github.com/apache/commons-compress/pull/113#issuecomment-730065042


   > My testing showed the TarFile and TarArchiveStream performance is 
equivalent for sequential access. The performance gain for accessing a single 
entry in the TarFile is huge because the TarArchiveStream needs to read and 
skip all data until it reaches the entry.
   
   > If you would like some numbers for some cases feel free to name them. I 
can create some benchmarks and share them with you.
   
   That's interesting. Would you please upload the tests so I can have a look? 


----------------------------------------------------------------
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: 513896)
    Time Spent: 4h 10m  (was: 4h)

> 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 10m
>  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)

Reply via email to