>> 1) Domino is running for a while. (After shutting down and startup
>> performance is better for a while)
> Domino is something I avoid. I don't think Domino lives well with other
> applications, which I believe is one of the reasons IBM came out with the
> dedicated Domino server.
Domino runs well on our 8-way 830 alongside all of our production apps. It
also runs just fine on our 270 that we use for webserving. On this
machine, we only use it for SMTP.
I believe, and I may very well be wrong, that Domino, like WAS, likes the
newer processors with more L2 cache. We also have a Domino 5.0.8 server
running on an old 170, and the thing barely crawls along. Domino is a pig.
Especially R5 compared to 4.x. I can only imagine what Domino6 will be
like. I imagine it will want a 12-way.
>> We have lost too much time 'waiting' and are planning to put Domino on a
>> separate machine in future. For now, we would like to install WAS on a
>> Win2000 machine.
> Good luck. Moving your web application development to Win2K is a bad
idea,
> in my opinion. I have seen no need for it. I suspect that if you
offload
> the Domino workload, you will find that WebSphere runs much better, and
you
> won't have to consider offloading to a Windows machine.
If you're on a 720, you DEFINITELY want to get Domino off there if you're
trying to run WAS as well. Get a DSD or a 0-interactive 270. Or throw
Domino on an NT/2K box. It's not as stable, but it does OK if Domino's not
mission critical and it's cheap. Clustering them isn't too hard if you
need high availability (so they say).
Mike Eovino
