<snip>
> Reason for Perl/CGI was that I didn't want to learn Java
> yet.
> Now just tonight I have seen the same application at a US
> Uni which runs on a
> browser and written as a Java Applet. It simulates 40
> molecules reacting with some
> nice graphics. My application simulates 10,000 molecules for
> around 30,000 to 50,000
> iterations and runs fine on my 233MHz 32Meg RAM Linux box
> here.
>
> You mentioned number crunching. Is Java up to it on your
> clients PC's?
I would say that if the same application was written using Servlets/JSP
pages instead of applets, you will achieve faster performance than Perl/CGI.
But, Java needs more memory than Perl/CGI.
I have done some perf test with Servlets against Perl, fastCGI and ASP pages
and Servlets trounces everything that comes along. Espeicially using a nice
mixed mode VM or HotSpot. Take the results after running the server for 10
mins. It will be faster.
Here are some benchmark results comparing from Caucho comparing servlets/JSP
vs mod_perl ...
http://www.caucho.com/articles/benchmark.xtp
For a good servlet engine go to
http://www.caucho.com
http://jakarta.apache.org
http://www.enhydra.org
-- Aravind
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
