Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Gold/Mining/Energy : A to Z Junior Mining Research Site -- Ignore unavailable to you. Want to Upgrade?

To: SI Bob who wrote (4642)	6/2/2003 12:28:18 PM
From: E. Charters	Respond to of 5423

You should talk to a few people before embracing windows servers. I know some real estate stuff on NT servers as I said at 1.5 million hits per day. The front end machine is Linux. It never burps. The NT machines are blue screened-rebooted constantly. I understand ASP need. It is hard to do micro changes in pages elsewise. It is a good "language" for page building too. Most pages here are static after a certain point, and used to be built I think from PERL. Bitch language. You could get speed up from C or C++ or any other server language. The real bottleneck though is page loads, and throughput. You can load a huge RAM base and serve from Squid, which caches pages in RAM.. Maximizing your trunk line capacity, and minmizing server load is next.. Multi servers is done, but they need a hand off server that takes requests.. I don't know how Squid would work with micro changes in pages.. updating.. it sort of is designed for static pages best.. Of course most of these pages are static once made.. You could still serve ASP pages from a Linux box could you not? Is it necessary to use an ASP server? I know Linux makes a better server of windows pages on a network than windows does, thru SAMBA.. EC<:-}