Wamp vs Production上的Mysql Innodb数据库

Question

i have 2 servers, one test one production.

1. Test - WAMP on Win7 (Intel i7 4GB Ram)
2. Production - IIS + FastCGI + MYSQL on Windows Server 2008 (Intel Xeon 2.4GHZ 12GB Ram)

We have an innodb database setup on both, and after deploying PHP source files, it would appear that a particular group of functions querying/displaying data from the database takes 100% LONGER on the production server.

On my test environment, I am seeing results come back after ~3 secs. On production, it takes ~10 secs for exactly the same query, with exactly the same source files and same mirror of dbase.

If anything, I was expecting for timings to be reversed, ie production 100% faster than wamp. I checked my.ini files on both sides, and although they are not the same obviously there is nothing glaringly wrong in there which would cause this. I tested with a few different configs of my.ini on production and this had no effect in reducing the processing times.

The query used for this test is a complex multiple loop which interogates the database (sends one query, then loops through results and does further queries to mysql server on each row) All results are kept and modified in memory using multidimensional arrays.

I am timing the actual script execution only (mysql + php data retrieve and process), not the time it takes to send this data to the browser :)

Where should I look next?

Answer 1

just to close this, it was due to the incorrect localisation within php environment - setting my locale at the top of the php page cured the problem. (despite it being correctly set within php.ini, IIS slowed down when performing date based functions) love microsoft