Just a point to make here, but I\'d like to get more details too.
A lot of posts I read seem to indicate that connection to MSSQL from PHP is slow. However, I saw a post on WEBLOGS that indicates that the connection to MSSQL is about the same as that to mySQL (on Win32).
Here is the link:
<!-- m --><a class="postlink" href="http://php.weblogs.com/adodb_benchmarks">http://php.weblogs.com/adodb_benchmarks</a><!-- m -->
An important note... the computer used for the bench is not exactly a server.
Now I will point out that the test makes use the ADODB package. I have yet to try it out, but it has a completely different set of calls... different than the ODBC or MSSQL calls that are part of the main PHP package. However it still works though the MSSQL7.dll
I\'ve worked only w/ PHP & mySQL on Linux and have known it to by lightning fast. Calls to a moderately sized db were in the sub second range. (PII 400 MHZ, 700+ MB RAM).
I\'ll be testing out the ADODB system next week. It will be on a Quad Processor NT 2000 System... I\'ll let you know how it goes. If I get 5 second retrevals... um, I\'ll be trying something else.
I also want to note that the first call to the db is always the slowest.
The other thing that I point out is this fact:
CGI PHP is slower than PHP MOD
PHP MOD for Apache is unstable
PHP MOD for IIs does not exist
So, one can only use, one who is in there right mind, the CGI PHP for IIS.
The biggest advantage of the Apache mod is that it allows for persistent connections.. and thus has lower overhead.
I wonder if the slowness that people are seeing in PHP w/ MSSQL is really just due to overhead from the IIS web server and not the bad link of PHP and MSSQL? It\'s probably a combo of several things because I seem to recall people using Apache and complaining about the same thing. Then again, I\'ve heard that apache is slow on NT.
In any event, we plan to try the WEBLOGS install next week.. I\'ll post back and let you all know if it A) actually installs and B) Gives me something to write home about.
However, I\'m afraid that the true fact is: PHP was never really designed to RUN on NT. PHP built a strong reputation from the mySQL/Apache combo. To say that it is going to be just as robust on NT remains to be seen. But considering the number of Unix developers vs NT developers, I suspect that it may be a while before the Win32 system builds a reputation worthy of its name.
I\'m interested in hearing others\' experiences with the PHP4-MSSQL-IIS setup.
Cheers,
M
A lot of posts I read seem to indicate that connection to MSSQL from PHP is slow. However, I saw a post on WEBLOGS that indicates that the connection to MSSQL is about the same as that to mySQL (on Win32).
Here is the link:
<!-- m --><a class="postlink" href="http://php.weblogs.com/adodb_benchmarks">http://php.weblogs.com/adodb_benchmarks</a><!-- m -->
An important note... the computer used for the bench is not exactly a server.
Now I will point out that the test makes use the ADODB package. I have yet to try it out, but it has a completely different set of calls... different than the ODBC or MSSQL calls that are part of the main PHP package. However it still works though the MSSQL7.dll
I\'ve worked only w/ PHP & mySQL on Linux and have known it to by lightning fast. Calls to a moderately sized db were in the sub second range. (PII 400 MHZ, 700+ MB RAM).
I\'ll be testing out the ADODB system next week. It will be on a Quad Processor NT 2000 System... I\'ll let you know how it goes. If I get 5 second retrevals... um, I\'ll be trying something else.
I also want to note that the first call to the db is always the slowest.
The other thing that I point out is this fact:
CGI PHP is slower than PHP MOD
PHP MOD for Apache is unstable
PHP MOD for IIs does not exist
So, one can only use, one who is in there right mind, the CGI PHP for IIS.
The biggest advantage of the Apache mod is that it allows for persistent connections.. and thus has lower overhead.
I wonder if the slowness that people are seeing in PHP w/ MSSQL is really just due to overhead from the IIS web server and not the bad link of PHP and MSSQL? It\'s probably a combo of several things because I seem to recall people using Apache and complaining about the same thing. Then again, I\'ve heard that apache is slow on NT.
In any event, we plan to try the WEBLOGS install next week.. I\'ll post back and let you all know if it A) actually installs and B) Gives me something to write home about.
However, I\'m afraid that the true fact is: PHP was never really designed to RUN on NT. PHP built a strong reputation from the mySQL/Apache combo. To say that it is going to be just as robust on NT remains to be seen. But considering the number of Unix developers vs NT developers, I suspect that it may be a while before the Win32 system builds a reputation worthy of its name.
I\'m interested in hearing others\' experiences with the PHP4-MSSQL-IIS setup.
Cheers,
M