Abhishek Reddy — Wed, 05 Jun 2002 08:22:48 +0000

You've got it the other way round.

The content, whatever it is, wouldn't count to badnwidth. The end results (the HTML, not the PHP code etc) is sent back to the client which uses bandwidth.
I think

I'm not sure about load time calculations.

Busy — Wed, 05 Jun 2002 08:17:22 +0000

So the contents, whether it be included or from database would count for server bandwidth but the end result (displayed page) wouldn't ?
so how would you work out load time for anything serverside related? It cant be put down to the servers machine as the client has to be considered as well

Abhishek Reddy — Wed, 05 Jun 2002 07:46:33 +0000

Server-side languages (hence, DB queries) and the like, run on the server before output is created.

I guess it's just the output to the client that counts towards bandwidth.

Similarly, includes are executed within the server, and the consequent HTML code is sent back.

As for caching includes and DBs; once again, the included file/DB itself isn't necessarily returned to the client.

I think some hosts charge for CPU (over)usage and slowing servers, so it's not always free.

Suzanne — Wed, 05 Jun 2002 05:56:19 +0000

I can guess at some of this -- there is a difference between CPU usage and bandwidth, meaning while the database is accessed, it's not all sent to the user with each call, so the include would count in the bandwith, but not the access of the db.

Yes, cache first, then server, depending on page, server, ISP, and browser settings. Included files aren't cached, but servlets are, sort of, and decrease CPU usage.

How's that for starters! Come on people, put me in my place, tell me where I'm wrong.