Here's a link that talks about the whole distributed architecture issue:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnile/html/docu2kbench.asp
(make sure there are no spaces in the URL)
Now, this is my 2 cents:
I use COM components for more than just business logic. COM components are compiled, so they execute faster then ASP scripts (even on IIS 5). I think that logical tier separation is important, which means there should be a dedicated presentation tier component that is responsible for generating HTML. My favorite technique is to have a tier that takes data from the business layer (which processes data appropriately from the data access tier) and applies an XSLT transform to generate the HTML, and send it directly to the browser (ObjectContext("Response").Write. If I want to change the presentation, all I have to do is plug in a new XSLT script file.
One last bit before I get off my soap box:
I've found that flexibility and maintainability are almost as important as performance. I've worked for a few dotcoms, and the business plan always changes. A component-based approach is easier to reorganize than modifying all you ASP files.
If you email me, I'd be happy to go on and on...
Good luck with your design.