![]() One of the reasons why I am still on exadel and myeclipse, which are reasonably fast and allow ligher containers to be plugged in. ![]() The answer is easy, it is the J2EE server which sucks up ram like no second app in existence (except websphere maybe), you deploy your small app, you start the app server, and from one minute to the other 700MBs are gone for stuff which you easily can plug into a lean container because it is sort of self reliant with dependencies only into the jsp and servlet part of J2EE and no option to remove the Sun app server and plug in a Tomcat. So why is it like that, that the Sun system comes to a crawl (have in mind this is a dev preview so things might change) ![]() So now I usually write JSF applications and most of my apps run on a standard tomcat with a mem setting of 128MB (if at all) and blazingly fast, doing orm mapping and transaction control on method level in the backend. ![]() An excellent tool, with excellent technology integration but as soon as you write some kind of JSF hello world with a bunch of controls, the system comes to a crawl. Sun Studio Creator 2 is the perfect example of this problem. One thing I noticed with most speed problems of those tools, was that it basically was caused by the underlying app server, or lets say memory consumption of it. Is one big problem of many j2ee tools, only a few got it right.
0 Comments
Leave a Reply. |