Re: Big Site !!!!
| From: | Michael Kimsal | Date: | Tue, 26 Sep 2000 13:50:22 +0000 |
| Subject: | Re: Big Site !!!! | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-17613@lists.php.net to get a copy of this message | ||
A bit off topic, but I've been in situations where people have
used this 'it'll slow the server' argument against SSI (then went
ahead and moved to NT/ASP anyway).
How much time does it take you to individually change and upload 300
files everytime someone makes a change? How much is that time worth?
How many times over the course of a year does this happen?
Now - calculate the speed difference of going to SSI (probably
less than you think). If you're sending that much DHTML that there's a
noticeable impact with SSI, then there's probably a noticeable impact
on downloading in general, and probably also on the client's end rendering
all that code too.
Now, figure out what it would cost to get a second server to
handle the same amount of requests at an equivalent, non SSI speed.
Or, if you're on an older server, see what it would cost to upgrade to a
faster processor.
Now, which one is cheaper? My guess is that upgrading your hardware
some to offset the SSI processing is far more cost effective in the long
run.
If *I* had to change 300 files by hand, then upload, I think it would probably
be at least 3 hours per month (figuring verification of changes as well). 36
hours per year. At, oh, say $20/hour labor cost. That's $720 (probably
more, but that seems conservative). Now, getting a second low end
web server should be less than $720.
Does this argument not work? Computers were supposed to save *us* time,
not us save *them* time. !!! :)
Hope this helps some.
Abe Asghar wrote:
> Hi there,
>
> I have another question:
>
> We are managing a rather large web site. There is a stangard navigation on
> the entire website. When our client requests a change to this - it is a
> monster to change because we have 300 files to change individually and
> upload.
>
> I recommended SSI's but was informed that this would cause problems for
> something as big as the DHTML navigation in terms of speed.
>
> My next suggestion was using PHP and functions to make lif easier.
>
> However the problem is that the site is already submitted to search engines
> and I have been told that many search engines do not look at PHP code.
>
> Does anyone have any suggestions about this. Any help would be kindly
> appreciated.
>
> Thanks
> Abe
--
==========================
Michael Kimsal
http://www.tapinternet.com
734-480-9961