Jul 012011
 

I was unhappy with the performance of our Drupal websites when using them logged in. We have a local test machine that is LAMP (Linux, Apahce, MySQL, PHP) and it was had page load times of over a second quicker than the production server that is WIMP (Windows, IIS, MySQL, PHP). While the machine are using different OS and Webservers that didn’t account for the issues. Using the Devel module it was telling me the MySQL queries were almost identical between the two machines but the page execution time was significantly slower on the production machine.

After using a profiling extension for PHP I tracked down the problem. PDO was taking over a second (!) to connect to the MySQL database on localhost. After much searching around it turns out the problem seems to be due to MySQL having issues with resolving names with IPv6 addresses. Windows Server 2008 R2 by default returns an IPv6 (::1) and IPv4 (127.0.0.1) address for localhost. In order to work around the issue I needed to add ‘127.0.0.1 localhost’ to the servers \Windows\System32\etc\hosts file. It should be noted for anyone else doing the same, make sure there is no IPv6 address for localhost in the hosts file either.

After making the change, database connections were instant and the performance of the sites improved considerably.

  One Response to “MySQL Dramas”

  1. I had the same problem as my R2 machine kept establishing TCP_IPV6 and this broke many applications that didn’t support it. You can always set windows to prefer ipv4 over ipv6 without doing anything drastic like your aforementioned.

    http://www.eggheadcafe.com/software/aspnet/29836859/this-article-shows-you-how-to-set-vista-to-prefer-ipv4-to-ipv6-when-attempting.aspx

    Nearly broke my server after unwillingly converted it to an ADDC.

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)