Since the automatic upgrade feature came out, I’ve always hesitated using it as on my test sites (and live sites) it just takes too darn long to run. I can manually upgrade faster. It generally takes about 15 minutes to run the automatic upgrade. I thought this was normal until I started talking to other people who were running the upgrade and it seems like this is way out of line from what most people are experiencing.
The server has plenty of power, and runs about 10 WP installations with over 100,000 page views per day. I have plenty of spare bandwidth, memory, CPU, etc. This really doesn’t seem like a resource issue.
There is nothing strange in my Apache logs related to the install– and the install goes through just fine. I just hate using the automatic upgrade feature because it takes too long.
While my Apache logs didn’t indicate any issues, I noticed in my FTP logs that it appears as if the upgrade isn’t simply downloading the zip, extracting it, and replacing files. Rather it looks like the incoming FTP connection is transferring over one file at a time, changing directories when done with one, then transferring over one new file at a time again.
Looking through my FTP logs, I saw 1,453 “STOR” commands related to the WP upgrade. I would have expected there to be one, for the zip file and then all of the files would have been moved around after.
Can anyone shed any light on why the upgrade is taking so long on my servers or any troubleshooting steps I can take?
- The topic ‘Why Does WordPress Automatic Upgrade takes 17 minutes?’ is closed to new replies.