ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 62995] Unzip performance regression on Windows due to BZ 62502
Date Tue, 11 Dec 2018 11:08:34 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=62995

Falko Modler <f.modler@gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #3 from Falko Modler <f.modler@gmx.net> ---
>> Is this target using "unzip" in just a basic manner or is there anything more to
it?

It's really just basic unzip.

>> I would expect the JRE implementation to return a cached value

Ok, maybe - I don't know. I just had a quick look at the code and did some
research on the method and found various blog entries etc. that contained a
warning that this method should be used sparingly.
If there is some caching, it must reside in native code. Another question is:
Does it cache sub-paths? Each file from a zip (normally) has an unique path
string...

>> Can you post the timings though, with 1.9.12 and 1.9.13?

I ran some tests and while there *is* a noticeable/distinct delay, it is *not*
"threefold" as I stated initially. I am not sure where/how I saw this massive
delay.

1.9.12 allowFilesToEscapeDest=false: ~8s

1.9.12 allowFilesToEscapeDest=true : ~8s

1.9.13 allowFilesToEscapeDest=false: ~10s

1.9.13 allowFilesToEscapeDest=true : ~8s

In the end this leaves us with a ~25% penalty.

PS: As I don't use standalone Ant, the tests were conducted with:
- maven-anrtun-plugin (with updated ant dependency)
- Maven 3.3.9
- Java version: 1.8.0_192, vendor: Oracle Corporation
- Default locale: de_DE, platform encoding: Cp1252
- OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"

Hardware:
- Thinkpad P51
- Intel Core i7-7820HQ
- 64GB RAM
- Bitlocker-enabled NTFS partition on a Samsung SSD 960 Pro 1TB
- Virus Scanner (McAfee) is *not* active for the involved files/folders

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message