velocity-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben <benja...@pcguy.org>
Subject Re: Switching from PHP to Java/Velocity, Performance?
Date Mon, 17 Apr 2006 03:58:14 GMT
Just speaking from experience, don't want to start any server wars here:) 
Had a high traffic site running on Tomcat and then switched to Resin and 
noticed the improvement, also mentioned this to somebody and he gave me the 
3x figure, guess the only way to know for sure for any specific 
site/application is to run benchmarks in both tomcat and resin and see which 
one works best for you.

----- Original Message ----- 
From: "Bill Rishel" <illusyn@gmail.com>
To: "Velocity Users List" <velocity-user@jakarta.apache.org>
Sent: Sunday, April 16, 2006 9:28 PM
Subject: Re: Switching from PHP to Java/Velocity, Performance?


I found this, which seems to contradict superiority claims
for Resin:
http://raibledesigns.com/page/rd?anchor=resin_slower_than_tomcat_fails

Bill Rishel

On 4/16/06, Andrew Mason <slackmase@gmail.com> wrote:
>
> Is resin that much faster ?
> On Sunday 16 April 2006 1:56 am, Ben wrote:
> > Just a thought: is there a specific reason you're using Tomcat and not
> > Resin? Resin is much faster than Tomcat, with some people saying it's 3
> > times as fast, so might be a quick and easy way for you to improve
> > performance.
> >
> > ----- Original Message -----
> > From: "Dominik Bruhn" <dominik@dbruhn.de>
> > To: <velocity-user@jakarta.apache.org>
> > Sent: Thursday, April 13, 2006 5:43 AM
> > Subject: Re: Switching from PHP to Java/Velocity, Performance?
> >
> > > Hy,
> > > thanks for all responses. As I have written PHP-Scripts for years I
> know
> > > the
> > > differences between writing a PHP-Script and writing a Java-Programm:
> > > Java forces you to write "better" code when PHP lefts the possibility
> to
> > > write "ugly" code. I also know the advandage of PHP: You can develop
> fast
> > > and
> > > don't need much knowledge to start.
> > >
> > > My plans were to Use a VelocityViewServlet and Velocity-Templates. In
> > > between
> > > a small layer for abstraction and Page-Handling and Permissions. As
> > > Database-Layer I use JDBC. I tired Hibernate but I haven't seen any
> > > advandages in it. I don't want to use Struts because I think its
> useless
> > > for
> > > me. The whole Servlet runs on a Tomcat-Container.
> > >
> > > When talking about the ability to cluster the Servlet in future I
> thought
> > > about the following solution: I two or more Tomcat's on different
> > > servers. Then I put a Webserver with Proxy-Support in front which
> > > distributes the Requests over the Tomcats. This seems a quite simple
> and
> > > fast solution. What
> > > are the point I have to think of when realising such a system? Where
> are
> > > the
> > > facts where the people tell that PHP ist better when using clustering?
> I
> > > cant
> > > understand this!
> > >
> > >
> > > Thanks
> > > Dominik
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: velocity-user-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org


Mime
View raw message