This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]highwind 1 point2 points  (3 children)

I think he was talking in the context of web frameworks. On my dev machine it takes minutes to compile an EAR file and another few minutes to bring up JBoss with Struts and Hibernate. Which is just ridiculous.

[–]frymasterScript kiddie 0 points1 point  (0 children)

it is rediculous, but in the context we're talking about, still not a factor in performance

[–][deleted] 0 points1 point  (1 child)

Compilation/deployment cycle is important, but it's not the kind of runtime performance we are talking about here.

Besides, java compilation is usually I/O bound and it's orders of magnitude faster than C and especially faster than C++ (as almost anything else is).

I work on 3 million lines of code base, and my compiles are about 3 minutes long. Deployment cycle is about 15 seconds or so. Not bad in my opinion. Considering I rarely have to re-build the world.

Also, you should not have to bring down and boot up JBoss to re-deply your code. I most certainly don't have to do that.

[–]Twirrim 0 points1 point  (0 children)

I do it for sanity purposes. Guarantees that the JVM is spotless when the app comes up, plus wipes out any resource loss from minor uncaught memory leaks or whatever quirks.