Tomcat vs glassfish performance archive#
Tomcat vs glassfish performance full#

I'm a little bit surprised, since I thought that using Tomcat would actually increase the speed due to it being more lightweight than Glassfish, since I'm not really using the advanced functionalities provided by Glassfish. In any case, there's a difference in performance of factor 10. The other times it takes about 20 seconds less, presumably because of the same reason. The same file on Tomcat7 takes about 90 seconds to upload and parse the first time.

Tomcat vs glassfish performance full#

I would prefer Glassfish 3.0.1 or even better 3.1 (currently beta/milestones), it is easier to administrate, has full JEE6 support with CDI, JPA, Transactions and so on. Unfortunately, i don't have a newer comparison. After that, it takes about 2 seconds less, due to the fact that I don't clean up the uploaded file (yet). This blog ist very old and not up to date. The largest testfile I have takes about 8 seconds to upload and parse on glassfish v3. Apart from a few small issues with Tomcat forcing me to add JSF dependencies despite the fact that I'm not using any JSF, there is one big issue I have with Tomcat atm. Tomcat has a lighter memory footprint ( 60-70 MB), while these Java EE servers weigh in hundreds of megs. Glassfish is a complete Java EE application server, including an EJB container and all the other features of this stack. It will generate an in-memory representation of these files, and write them to a Neo4J Graph Database, currently in embedded mode.ĭuring development, I used a GlassFish v3 but with production in sight, the request has been made to move from Glassfish to Tomcat and so I did. Based on source code released by Sun and Oracle, it uses a derivative of Apache Tomcat as the servlet container for serving Web content, with an added component. Primary Difference between GlassFish and Tomcat Tomcat is simply an HTTP server and a Java servlet container.

Tomcat vs glassfish performance archive#

The application will then unzip the archive which contains XML files, and parse them using basic SAX parsing.

I have a simple JSP/Servlet maven application which allows a user to upload an archive file.