On Tue, 2006-09-05 at 17:17 -0700, Rohit Seth wrote: > I'm wondering why not have different processes to serve different > domains on the same physical server...particularly when they have > different database to work on.
This is largely because this is I think how it is done today, and it has a lot of disadvantages. They also want to be able to account for traffic on the same database. Think of a large web hosting environment where you charged everyone (hundreds or thousands of users) by CPU and I/O bandwidth used at all levels of a given transaction. > Is the amount of memory that you save by > having a single copy that much useful that you are even okay to > serialize the whole operation (What would happen, while the request for > foo.com is getting worked on, there is another request for > foo_bar.com...does it need to wait for foo.com request to get done > before it can be served). Let's put it this way. Enterprise databases can be memory pigs. It isn't feasible to run hundreds or thousands of copies on each machine. -- Dave ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
