Bug 1449932 - [GSS](6.4.z) Performance problem in JarFileResourceLoader
Summary: [GSS](6.4.z) Performance problem in JarFileResourceLoader
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: MSC
Version: 6.4.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.16
Assignee: Radovan STANCEL
QA Contact: Jiří Bílek
URL:
Whiteboard:
Depends On:
Blocks: eap6416-payload 1448486 1465995
TreeView+ depends on / blocked
 
Reported: 2017-05-11 07:59 UTC by tmiyargi
Modified: 2021-06-10 12:18 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-06-22 09:21:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-10942 0 Major Verified (7.0.z) Performance problem in JarFileResourceLoader 2018-04-20 09:59:25 UTC
Red Hat Issue Tracker JBEAP-10943 0 Major Verified (7.1.0) Performance problem in JarFileResourceLoader 2018-04-20 09:59:25 UTC
Red Hat Issue Tracker MODULES-284 0 Major Resolved Performance problem in JarFileResourceLoader 2018-04-20 09:59:25 UTC
Red Hat Knowledge Base (Solution) 3084361 0 None None None 2017-06-19 07:58:26 UTC

Description tmiyargi 2017-05-11 07:59:48 UTC
JarFile and ZipFile lock for just about anything. EAP deployment iterates many shared modules, all of which are backed by JAR files. Deploying many archives in parallel can cause massive contention on these JAR files from iteration operations.
We don't need to iterate the JarFile every time; we can just grab a snapshot copy of the list of regular files in the JAR and traverse that instead.

Comment 1 tmiyargi 2017-05-11 08:02:15 UTC
Upstream https://issues.jboss.org/browse/MODULES-284

Comment 4 Jiří Bílek 2017-06-19 10:13:26 UTC
A speed of deploying was increased -> Verified with EAP 6.4.16.CP.CR1

The fix causes increase of memory usage by cca 10MB.

Comment 5 Petr Penicka 2017-06-22 09:21:05 UTC
Released on June 20 2017 as part of the EAP 6.4.16 maintenance release.


Note You need to log in before you can comment on or make changes to this bug.