We've migrated our Drupal 7 setup from one WAMP box to another. Apache and MySQL are on separate boxes. Page load times are terrible (approximately 11 seconds for each page load) additionally for one single page hit CPU on the apache.exe process spikes to 75%. I'm running Apache/2.4.3 (Win64) PHP/5.4.5.
The searching I have done has indicated this can be a problem with a module and to try disabling modules. Unfortunately I have 133 modules and if I disable them all my pages don't load at all. I even tried disabling all but the default modules and still I'm having problems.
I've ready about using XHPROF but since I'm using x64 apache on windows I can't find an appropriate binary to use. I've also enabled the devel module and I'm not seeing any obvious culprits there either.
I've also tried using the following patch which seems to have made no difference: http://drupal.org/node/1081266
A fresh install of drupal with a clean database seems to work considerably better which makes me think this is an issue with our data vs the server configuration itself.
Is there anything special I need to do when migrating data from one database server to another? What else can I do to troubleshoot?
After doing some more testing it appears the issue is that of SMB vs local storage. When I store my files on local storage load time is 4-5 seconds. When I store it on a UNC/SMB location load time increases 3-4x as long.
The reason for using SMB/UNC is so that multiple load balanced servers can access the same set of shared content. So I suppose I might next ask:
- Is there some way to improve the performance of SMB?
- If not, what other options exist? I've heard horror stories about NFS and RSYNC'ing files.
So what is the best way to scale?