Issue Details (XML | Word | Printable)

Key: SPR-4990
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Major Major
Assignee: Juergen Hoeller
Reporter: Jorg Heymans
Votes: 1
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
Spring Framework

huge difference in hot deploy times on Weblogic for 2.5.5 vs 2.0.8

Created: 08/Jul/08 06:29 AM   Updated: 23/Oct/08 10:05 AM   Resolved: 01/Sep/08 06:48 PM
Component/s: None
Affects Version/s: 2.5.5
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: 1. Text File output.log (292 kB)
2. Text File outputGC.log (110 kB)
3. Text File outputGC2.log (462 kB)
4. File weblogic9.2MP2-spring2.0.8.z01 (9.00 MB)
5. File weblogic9.2MP2-spring2.0.8.z02 (9.00 MB)
6. Zip Archive weblogic9.2MP2-spring2.0.8.zip (77 kB)
7. File weblogic9.2MP2-spring2.5.5.z01 (9.00 MB)
8. Zip Archive weblogic9.2MP2-spring2.5.5.zip (8.93 MB)

Environment: Windows, development environment

Virtual Machine: Sun JVM - 1.5
Platform: BEA WebLogic - 9.2


 Description  « Hide

Hi,

I upgraded one of my 2.0.8 applications to Spring 2.5.5 just by replacing the old spring-2.0.8.jar with the new spring-2.5.5.jar and spring-webmvc-2.5.5.jar. As a result, the hot deploy times increased drastically. The application was otherwise unmodified , so we're definitely not using any specific 2.5.5 features (i.e. component-scanning)

Here are some timings from my local machine (win xp), the application is deployed as an unpacked WAR in Weblogic's autodeploy directory. I hotdeployed the app 5 times in sequence, without making any request to the application in between. Timings are taken from the "Root WebApplicationContext: initialization completed in X ms" message. The server was restarted and WLS jar caches were cleared in between runs.

2.0.8 (ms)
6562
6000
5969
6844
6894

2.5.5 (ms)
27203
28532
32141
34345
32562

There is an almost 500% increase in deploy time. Also, I noticed that the 2.5.5 deployment time seems to increase with the number of times deployed (it went as high as 38s).

http://forum.springframework.org/showthread.php?p=188252 seems to indicate something similar, but he's using component-scanning.

If there is anything I can do to troubleshoot this or provide more information let me know.

Thanks,
Jorg Heymans



Juergen Hoeller made changes - 09/Jul/08 11:53 AM
Field Original Value New Value
Fix Version/s 2.5.6 [ 10968 ]
Assignee Juergen Hoeller [ juergen.hoeller ]
Jorg Heymans made changes - 10/Jul/08 04:33 AM
Attachment weblogic9.2MP2-spring2.0.8.zip [ 14341 ]
Jorg Heymans made changes - 10/Jul/08 04:34 AM
Attachment weblogic9.2MP2-spring2.0.8.z01 [ 14342 ]
Jorg Heymans made changes - 10/Jul/08 04:35 AM
Attachment weblogic9.2MP2-spring2.0.8.z02 [ 14343 ]
Jorg Heymans made changes - 10/Jul/08 04:38 AM
Attachment weblogic9.2MP2-spring2.5.5.zip [ 14344 ]
Jorg Heymans made changes - 10/Jul/08 04:38 AM
Attachment weblogic9.2MP2-spring2.5.5.z01 [ 14345 ]
Jorg Heymans made changes - 11/Jul/08 02:38 AM
Attachment output.log [ 14347 ]
Jorg Heymans made changes - 16/Jul/08 02:27 AM
Attachment outputGC.log [ 14390 ]
Jorg Heymans made changes - 16/Jul/08 03:21 AM
Attachment outputGC2.log [ 14391 ]
Juergen Hoeller made changes - 01/Sep/08 06:48 PM
Fix Version/s 2.5.6 [ 10968 ]
Resolution Won't Fix [ 2 ]
Status Open [ 1 ] Resolved [ 5 ]