Mein Artikel “Improving Glassfish Deployment Performance in Eclipse” aus der englischsprachigen Sektion von jars.de hat es in das Glassfish Aquarium “geschafft”. Zusammengefasst ließ sich die Deployment-Geschwindigkeit mit zwei einfachen Mitteln um 40% erhöhen: Zum einen hilft ein simpler Ant-Task für Verzeichnis-basiertes (exploded) Deployment und zum Anderen den Virenscanner feintunen. Das Directory-Deployment hilft auch bei der JSP/JSF Entwicklung, da Änderungen an JSPs ohne Redeployment sofort sichtbar werden. Die Details sind im englischsprachigen Artikel nachzulesen.

It’s well know that Netbeans supports Glassfish very well. One of the features I like most is incremental deployment, because it can save you a lot of time during development. Adam Bien posted some performance figures. Even for a large project it takes just 6 seconds using Netbeans’ incremental redeployment.

Compared to Netbeans, Eclipse with WTP seems to offer only 2nd class support for Glassfish. Unfortunately, this did not change with Eclipse 3.4 and WTP 3.0. For example, directory deployment is not supported. Publishing a EAR project to Glassfish always implies creating a new EAR File. I played around with it a bit and decided to switch back to ant. It requires just a simple ant script to copy the files into a directory structure and to call asadmin deploydir. This reduced deployment time by 20% for my EAR project. Another advantage of exploded directory deployment is that changes in JSPs (including JSF) do not require redeployment. Changes are immediately visible after copying the JSP files.

The next observation was that antivirus software had a major impact on deployment performance. Den Rest des Eintrages lesen »