4 ms·
It doesn't give you that much. Servlets (kind of a CGI for Java) and JSPs, which you can use as a simple template engine or to interweave Java and HTML code (ki
by Tobias42 17y ago
It doesn't give you that much. Servlets (kind of a CGI for Java) and JSPs, which you can use as a simple template engine or to interweave Java and HTML code (kind of like PHP). An ORM is not included for example.
But the point is: If you add additional stuff, the larger part of the memory footprint of that additional stuff is only added once, because you don't need a new Tomcat for every request which you process in parallel, but only a very lightweight thread.
- davidw 17y agoOk, fair enough. Does that hold true when you load it up with stuff to make it an apples-to-apples comparison, though?
- Tobias42 17y agoIt depends on the number of parallel request you want to handle. I don't know where the break-even in favor of Java is, but I guess it is a low single-digit number of threads.
- nl 17y agoI've got "loaded up" web application running fine in 128M RAM. (Where "loaded up" equals a lot more than Rails/Django/etc gives you out of the box. We have a separate Tomcat running with a Solr instance for search, but that's for deployment reasons. If we put that in the same Tomcat I might push the RAM up to 192M, but it would probably be fine as it is)