![]() ![]() I tested all servers with default configuration, except for the hot-deployment scanning intervals decreased to a minimum for faster deployments (see directory “ server_configurations“). IBM JDK 1.7 64-Bit (used for WAS classic).IBM J9 JVM build R28_Java8_SR1_20150513_0846_B248471 64-Bit (used for Liberty Profile – by the way – for Liberty this showed slightly better results than Oracle JVM).Oracle JDK 8u60 64-Bit Server VM (used for Tomcat, TomEE, Jetty, JBoss EAP, WildFly, WebLogic, GlassFish). ![]() 64 bit Cygwin – all tests were ran in Cygwin using my own set of bash scripts posted on GitHub here.Windows 7 64-bit native install, 6.8 Windows Experience Index.Lenovo ThinkPad W530, 2 CPUs 2.6Ghz (4 cores, 8 hyperthreaded cores), 16 GB RAM, Samsung SSD 840 PRO 256GB (same machine I had 2 years ago – perhaps time for an upgrade if my manager is reading this? □ ).The test environment consisted of the following: Oracle WebLogic 12.1.3 (developer zip package).In this post I will show the results of my latest tests comparing the startup times, application deployment times, memory and disk footprint, and other developer focused characteristics of the latest versions of these products: The point of this research was to measure the typical developer experience, not a “benchmarketing” with lots of tuning and special tricks to make certain application servers run faster simply for the sake of faster numbers – hence I tested servers with little or no changes to their default configuration. It’s been two years since I wrote the original article comparing Liberty Profile, WAS classic, Tomcat, Jetty, WildFly, JBoss, GlassFish and WebLogic from a developer point of view. ![]()
0 Comments
Leave a Reply. |