The Latest Articles:

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

Thanks for letting me return to my youth and enjoy that momentary trek back in time.

Yesterday I wrote about Wordpress Version or GoDaddy Hosting. I love how quickly Google indexes some things and already today had a response by comment from someone at GoDaddy and a missed call (I was at the Dr. office, they don’t like cell phones there much) and a second comment in response from the person at GoDaddy leaving the comment. The tech from Godaddy said he would call me later this evening to see if he can help address the slowness of the blog.

Here are some of the things I’ve done today which have had some effect but not the kind Kirk wanted from Scotty.

  1. Google Gears was already installed, but I was using the Flock browser and not FF. I’m using FF. (Still like Flock better)
  2. I removed all plugins that were not being used. I have tested a lot of them over the past couple of years and removed everyone not in use.
  3. I took out the database calls in the header file and replaced them with static HTML
  4. I installed the Dashboard Management Plugin and removed almost everything from the dashboard except incoming links and write new post
  5. I created a new database on a different server backup the lab database and restored on the other server (clean lay down of the data)
  6. Tied to 5 above, the new database is MYSQL 5.0 the old one was 4.0 The new server is PHP 5 the old one was PHP 4
  7. I activated the WP Super Cache plugin and configured it.

Most of these are considered to improve load times rather than navigation inside the admin panel or editor. The saves in the editor and navigation from editor, to comment management, to dashboard, to plugins is where a lot of the wait time comes in.

By putting the database on another server I split the calls to the server between images and database calls which are not on two separate servers.  Of course the down side: “Now I have to have two servers functioning to load the blog.” HUM!

I just pressed “Save” and it took 20 seconds for the save to take place and the editor to be available to continue.  I think some of this must have to do with saving Post Revisions of a single post.  I really wish this was an option to be turned off.

I also wrote a quick draft post in a 2.2.2 WP blog today and none of these issues were apparent.

Google Gears  Auto Save and Post Revisions

I thought Google Gears was to move much of the editing functions to my HD, yet with every save or move I see “Waiting on www.realestatebloglab.com” at the bottom of the screen.  The only thing it should be doing there is saving the post.  I get the same message when opening a blank editor to write a new post.  I also wish I could set the time between auto saves because it save a lot and hesitates while doing so.

Comparative Load Times

I have to wonder if WP wasn’t experiencing some of these issues in development. Maybe that’s why we even have the TURBO option. I hope this is something that can be addressed in the next release, but I fear it is going to be more bells and whistles with more whistle time while waiting.

Save and Log In Again.

Finally ready to preview this post, pressed Save once again and after 30 seconds was sent to the login screen.  After logging back in there were a couple of words missing from my last edit.

Maybe all these auto saves aren’t such a bad idea after all.

Have a great evening, I’m going to go watch Dirty Harry for the fifth time this week.  I think it is the “Dead Pool” tonight.  I feel like I’ve been swimming in it all day.  Oh, Geez here goes another attempt at save.