Awesome! 8)
Sorry, I just did another quick reboot.
Thanks SB, for the record, mine showed updated this afternoon, even before the site was actually up. 
Really appreciate all the hard work, would be lost with you!
Looks good to me.
Fast! Much faster than the last two servers.
"Mark All Read" used to take 20-30 seconds. Now it takes 1 second.
Thanks for saying so. I’m not sure yet how it’ll hold up under normal load, since it’s early morning in North America and some of our users are still waiting for a DNS refresh.
I’m still tweaking stuff, hence the frequent little blips of downtime.
Are you asking us to load test it?
alright guys, forget work today, we’ve got some real work to do. Let’s get those post counts up! 
Just normal load! (As in, “use the site”.)
Faster than it was
Feels quicker here.
Thanks Mr. Admin. And sorry that there have been so many hassles along the way.
very smooth,well done sofar :-)
Thanks to everyone for their reports! I’m going to give it one more reboot and call it good for now.
Yeehaw BLF is back...
Oops. Got a timeout enduring sending of a PM... not back 100% yet.
Yay! :party: Thank you for your hard work, Sb!
Is anyone else finding the forum slow to load/stuck loading, e.g. recent posts, showing thread after commenting, etc.?
yepp... me..
I even have times I cant even open BLF...
I am finding things a little slow when logged in e.g page refresh looking as if it might time out, erratic display of comments in threads.
like clicking on the Op title gets it jammed…but faster when clicking on the latest post count number instead.
Yup, I've been noticing the same intermittent hangups. Sorry, it's rather hard to know which settings are optimal until the site is actually online and being used in a normal fashion. So as more and more users are getting the new DNS update and visiting BLF on this new server, I'm testing how it reacts and tweaking a bunch of different settings. I wish there was a way to configure it, enable it, and let it run smoothly from the moment of activation, but unfortunately it requires more than a little trial and error with a new setup. Thanks for reporting your experiences, they are very much appreciated!
Just now you probably felt another reboot. (Geeky: Why reboot after changing a setting instead of just restarting the service in question? Because some of these changes also affect memory consumption, and I'm trying to get an idea of how much memory is being used initially with my configuration on a fresh boot and how much is used after it warms up. Linux caches so much stuff that sometimes it's hard to tell how much is actually being consumed by a recent change unless I reboot.)
Nice job, SB! I know it's not easy but you might be getting to be an old pro at this point. :beer: