All things being equal as your test environment (i.e. hardware, load), the big difference is latency on the network. You may have designed your application to "echo" code to the client as you create it. This may cause lots of small network packets which will slow things down considerably. You should build your web page and then send it all at once, either through output buffering or by storing everything in a variable and "echo"ing the variable at the end. This also allows you to take advantage of compression available in the HTTP 1.1 spec. Try and get you code so that a single line delivers the whole page to the client.

Think of it as someone saying "repeat after me". Then they proceed to say one word at a time, waiting for you to say the word before they move onto the next one. There is a lot of latency, pauses between words and response, in that technique.


On Aug 5, 2004, at 6:47 AM, Vinayakam Murugan wrote:

Hello

I am a fresh PHP programmer and am part of a team developing a LAMP based
website. The problem we are facing is that when the site was hosted on a
local server, it was quite fast. Now that we have to use the internet to get
to it, it has become very slow even keeping in mind considerations like
connection speed .


Any pointers on what & how optimizations can be done?

--
Warm Regards
~~~~~~~~~~~~~~~~~~~~~~~
Vinayakam Murugan

Tel: 91-22 - 2288 2163 Ext 121
Help Desk: 91-22 - 2288 2774
Fax Number: 91-22 - 2288 2809
Mobile : 022-31018082

http://www.TheArgonCompany.com

Viruses getting you down?
Get your virus protected mailbox at http://www.tassm.com

Linux. The Choice of the GNU generation

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


--
Brent Baisley
Systems Architect
Landover Associates, Inc.
Search & Advisory Services for Advanced Technology Environments
p: 212.759.6400/800.759.0577

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Reply via email to