Other people have made similar arguments, but just thought I'd throw in my 2c:
I had a couple of years experience running MySql (3.22.something) on
WinNT4sp5, 3-4 years with PHP as a CGI (going all the way back to
PHP2 aka PHP/FI) and ~9 months using Apache/PHP on Windows. As of
last fall, I have no Windows machines anymore, so my recollection at
the moment of details/versions is a bit fuzzy.
At 5:30 PM +0100 4/10/02, Mallen Baker wrote:
>Hi - the company we're talking to about doing some work on a simple
>site / database is trying hard to persuade us that Windows-based PHP
>/ mysql is not the route to go. The arguments are as follows:
>
>1. XXX's experience that MySQL is less than 100% stable when running
>on a windows platform (main problem being unexpected database
>shutdowns while applications are being used).
While I had fairly modest database usage, I NEVER had a single
problem with MySQL/Windows. It was fast, took up very little memory,
was about as close to set-and-forget as I've seen.
>2. The fact that the recommended mode for running PHP on a windows
>platform (the CGI binary) uses technology that is now reasonably old
>and will consequently result in a hit to the server performance and
>memory management and the associated possible lack of scalability.
As others mentioned, this is obsolete info; I migrated sites running
on Netscape Enterprise 3.5 & IIS to Apache with the PHP module (I
believe the versions were 1.3.20 & a fairly early PHP4) with few
problems (the biggest of which were a few functions that didn't work
as expected in a PHP release candidate, but there were simple
workarounds and - well, it was a release candidate not a final
release). I used the PHP modules from PHP4WIN:
http://www.php4win.de/
By the way, the Apache/PHP-based solution worked much better than the
ColdFusion stuff I was running on the same server. Cold Fusion sucked
up tons of RAM, and on occasion database queries on an Access
database caused CPU usage to spike at 100% until I restarted the CF
server.
If you want to use PHP with IIS, then it is my (likely obsolete &
incorrect) understanding that the PHP ISAPI version is still somewhat
experimental, and that CGI is the recommended approach there. But
then, I would avoid IIS as a web server to begin with.
>3. Loss of verity - the powerful search engine bundled with Cold
>Fusion. Searches may be significantly slower on the new site.
I'm sure you could still use Verity, but yes - you'd have to purchase
it separately. I had just started using htDig -
http://www.htdig.org/
- as a search engine on the Windows box, but I didn't get much of a
chance to get production experience with it. There's also MnoGoSearch
-
http://www.mnogosearch.ru/
- which looks promising (and is pretty popular on the Unix side), but
I don't have any experience with it. And, I think there's some
nominal license fee to use it on Windows.
Thus endeth my spiel -
- steve edberg
--
+------------------------------------------------------------------------+
| Steve Edberg [EMAIL PROTECTED] |
| University of California, Davis (530)754-9127 |
| Programming/Database/SysAdmin http://pgfsun.ucdavis.edu/ |
+------------------------------------------------------------------------+
| "If only life would imitate toys." |
| - Ted Raimi, March 2002 |
| - http://www.whoosh.org/issue67/friends67a.html#raimi |
+------------------------------------------------------------------------+
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
