You can never be too fast - Page 3

by HB on Thu Jan 15, 2009 10:12 pm

sweaner wrote:Ironically, Coffeegeek has been faster the last few days.

Perhaps you should spend more time there.

by **sweaner** on Fri Jan 16, 2009 5:38 pm

Dan, not even close!! Are you trying to give me a hint?

by HB on Fri Jan 16, 2009 6:21 pm

Oh bother.

General Error
SQL ERROR [ mysql4 ]

MySQL server has gone away [2006]

An SQL error occurred while fetching this page. Please contact the Board Administrator if this problem persists.

I've seen this error a few times in the last two days.

It is looking more and more like grid hosting = gridlock and that the more traditional approach may be necessary. If the site performance hasn't settled down by mid-next week, I'll pull the plug on this experiment and revert to a dedicated server with more memory. This time around I'll handle the DNS business more elegantly by keeping both servers up but pointing to the same database, so it won't matter if there's a propagation delay.

by **mute** on Fri Jan 16, 2009 6:28 pm

Eww, MySQL 4!

by **ntwkgestapo** on Mon Jan 19, 2009 4:50 pm

Dan, one EASY way to fix the DNS issue is to, at least 1.5 TTL (Time To Live) periods BEFORE the change (in other words, if you have a TTL of 86400 seconds [1 day] then, at least 1.5 days before REDUCE the TTL to 300 [300 seconds, 5 minutes]). The reason for this is to insure that DNS changes propagate out fairly quickly (and reversion BACK, if needed, happens quickly as well!

). THEN, 24-36 hours AFTER you're sure the change is "good" you can revert back to the standard TTL of 86400 seconds. This reduces DNS traffic back to a more "normal" level.... NOW, one "problem" with this is that Windows, in it's infinite wisdom, pays little to NO attention to the TTL values (I've got servers on our internal network that have NEVER updated their DNS entries, even 3 years later, for a system that had a 300s TTL SPECIFICALLY because the DNS entry pointed to 2 or more systems for a crude form of "load balancing"). Vista has FINALLY, apparently, done SOME towards that, but.... YMMV.

I did actually get a fairly good response for just a short period today... Went to a specific forum subject, which loaded in about 2-2.5 seconds and then forced a refresh of the base web site which, again, did complete in about 2-2.5 seconds... never happened again, unfortunately! Oh Well, C'est La Vie!

IF you have any questions on DNS "stuff" just ask. I've been involved in DNS stuff since the middle '80's!

by HB on Mon Jan 19, 2009 4:59 pm

I'm on the fence with respect to this new server.

Most of the time it's quite zippy. Some of the time, I see MySQL errors, something that was fairly rare before the migration (and points to a backlevel version of MySQL in their base install as "mute" noted above). I cannot explain the slowdowns you're seeing. The last of the problematic locales like VPN that I use figured it out late last week.

by HB on Tue Jan 20, 2009 11:17 am

The grid hosting isn't working...

Overall speed: very slow, current page: 44.4s, avg: 44.9s, max: 160.1s

by HB on Wed Jan 21, 2009 9:59 am

More hills and valleys:

Overall speed: fast, current page: 0.2s, avg: 0.2s, max: 0.6s

I think migrating to a dedicated server is the only long-term option. The idea of grid hosting sounds great on paper, but their implementation of it doesn't scale properly. I've prepared a new server and will switch the DNS entries tonight. Any suggestions for reducing the propagation delay other than tweaking the TTL value to 300 seconds? There's other TTL value like SOA TTL and secondary DNS values; I haven't fussed with them...

by **ntwkgestapo** on Wed Jan 21, 2009 10:17 am

Dan, IF you've got some time, give me a call... I'm available from 10am until 2:30. I'll PM you with my #'s

by HB on Wed Jan 21, 2009 11:28 pm

Thanks to a pep talk from Steve, I think the DNS updates will propagate faster than last time. According to InternetSupervision, 9 of their 10 worldwide sites are getting the right server (inexplicably Washington, DC is returning "cannot resolve DNS"). The next question is whether it was worth the time, effort, and money...


Contact Us	Legal disclaimer and copyright: This content and all its parts are copyrighted, all rights reserved. Content including all text and images in part or in whole may not be reproduced in any electronic or printed medium without prior permission. Home-Barista, Home-Barista.com and related logos are trademarks of Home-Barista.com, LLC. Other trademarks are the property of their respective owners. By accessing this site, you agree to the terms of service. Overall speed: , current page: s, avg: s, max: s