Okay, okay, not wanting to get into a big debate here - it was just a 
suggestion based on things we've done quite successfully, but just to point out 
a few facts...

> #1 it is quite likely that the DNS caching IS an issue, as who knows how PHP 
> handles the
> DNS. (hence this is why it improved dramatically when the host was defined in 
> the hosts
> file on the PHP server.)

Actually, the TCP/IP layer does the caching of IP addresses, not the 
application layer. That's one of the reasons the entire Internet is as scalable 
as it is. If every time someone makes a request, it has to revisit the DNS, the 
whole thing would not be sustainable. Wanna see what hosts your computer is 
currently caching? Just type ipconfig /displaydns into the command prompt.

> #2 Moving processing in the client is going to slow things down 
> dramatically... you
> have (probably) 100Mbits between the 2 servers and what to the client 
> exactly? 100k at
> best?  You're doubling the number of requests on the slower link, effectively 
> doubling
> your data transfer costs.

Think again. No matter what you do, you still basically have to move the same 
amount of content down the narrow pipe to the user. Having a fat pipe between 
the two servers is fine, but you still eventually have to get it down to the 
user. Spreading out the load into 2 separate http requests may in some cases be 
better (same reason why it's better to break up a large image into multiple 
fragments).

#3 CPU load for including data is not that great.
That is true, provided the included content is at hand. Otherwise we wait till 
it gets here.

Regards: Ayudh

+----------------------------------------------------------------+
| SOAP is the glue! Hook up your server directly to your bank.   |
| Connect to VeriPay xServ, the Australian Payments Web Service. |
| Reliable, Secure, FAST: http://www.xilo.com/xserv              |
+----------------------------------------------------------------+

        

---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to