>>I thought splitting my app between two machines should also give >>me a significant performance even though the serialization overhead, >>shouldn't it?
This was believed to be true early on in J2EE (1999-2000), but now most vendors advise in-JVM web and EJB containers to minimize the marshalling/unmarshalling overhead. Where's your web server (e.g., Apache, etc.)? You could use the extra box as the web server, which is a good idea if you use SSL since SSL is so resource intensive. In this case, you'd have Apache w/ SSL on a separate box to prevent hogging resources from your app server. my 2 c, Jason -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Pavel Kolesnikov Sent: Thursday, November 21, 2002 9:01 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] configuring security if web and ejbs on different machines OK, thanks for you response, I understand your point. But what should I do, if there's a need for better perfomance and customer says "well, I could buy another CPU or more RAM, but I have also an extra unused machine here - couldn't we use it instead of buying new CPU or RAM?" Should I try to explaint him it's not a good idea? I thought splitting my app between two machines should also give me a significant performance even though the serialization overhead, shouldn't it? Pavel On Thu, 21 Nov 2002, David Ward wrote: > Maybe I'm coming in late on this thread... > > What *I* don't understand is why you think having your web container on > one machine and your ejb's on another would perform better. Having your > servlets run in the same JVM as your ejb's allows your servlets to > access them with local interfaces, and you can pass your objects by > reference instead of by value (read: serialization unecessary). You > will get much better performance if everything is in the same JVM. Just > beef up your box instead of spending $$$ on two. > > Now, if you want to have Apache serve up some static content and front > your app, that's fine (especially if for security reasons you want your > app server behind a firewall and your web server in the dmz). However, > it will forward dynamic requests to your app server - where your web > container and ejb tier coexist in the same process. > > David > > -- > > Pavel Kolesnikov wrote: > > On Wed, 20 Nov 2002, Dain wrote: > > > > > >>There is no reason you have to separate the web container from the EJB > >>container. > > > > > > I don't understand this - what if I want to run my application > > on two machines because of performance reasons? What should > > I do instead of putting my webapp on one machine and my EJBs > > on the second one? > > > > Pavel > > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
