There will be some offline time today at about 10eastern.
Addressing a couple hardward issues.
Brett_Tabke
4:44 pm on Dec 22, 2011 (gmt 0)
baaaaaaaaaack.
incrediBILL
4:48 pm on Dec 22, 2011 (gmt 0)
This thing is REALLY fast now!
WOO HOO!
Marshall
4:51 pm on Dec 22, 2011 (gmt 0)
Here I though it was me. Shame on you Brett.
Marshall
Leosghost
4:56 pm on Dec 22, 2011 (gmt 0)
That was fast ( a "blink" in downtime )..now even faster :)
Brett_Tabke
5:09 pm on Dec 22, 2011 (gmt 0)
new mb/cpu/16gig ram.... same hd's.
Thanks LiquidWeb!
Panthro
5:11 pm on Dec 22, 2011 (gmt 0)
was wondering about that
ken_b
5:17 pm on Dec 22, 2011 (gmt 0)
> 16gig ram
Is that a big increase?
Seems a lot faster at he moment.
Brett_Tabke
5:28 pm on Dec 22, 2011 (gmt 0)
we were at 8gig. and never were using more than about 2 gig of it. then we added wordpress on the pubcon.com side a year ago and we regularly max out the ram. (even though pubcon.com does one 20th the traffic of WebmasterWorld)
Panthro
5:41 pm on Dec 22, 2011 (gmt 0)
Gotta love WP
rocknbil
5:42 pm on Dec 23, 2011 (gmt 0)
<Loves L.W.'s smart servers> :-)
coopster
8:00 pm on Dec 23, 2011 (gmt 0)
then we added wordpress on the pubcon.com side a year ago and we regularly max out the ram. (even though pubcon.com does one 20th the traffic of WebmasterWorld)
You should start a thread in the WP Forum about this beautiful feature.
I would probably assume it's MySQL hogging the memory but it's most likely something WP did inefficiently causing the problem.
nmjudy
7:18 pm on Dec 31, 2011 (gmt 0)
I stumbled across a post that I bookmarked (if I ever need it). It's called "Wordpress performance: Why my wordpress site is so much faster than yours". If you Google that query, you'll find it. The steps were a bit over my head, but I'm sure it will make sense to you smart guys. :)
I'd be interested in what you think of the article...
Brett_Tabke
2:26 pm on Jan 10, 2012 (gmt 0)
> MySQL hogging
That's part of it, but the plain fact is that the style of FUNCTION'crazy/procedural php coding of Wordpress makes for slow executing code. (Especially when compared to zippy straightline/subroutine oriented code of WebmasterWorld's perl code). I would bet the average call to wordpress takes 20-30 times the amount of overhead code that we take here.
You can get around the mysql problems with caching. However, if you are running dynamic served ads or random content, then caching can actually SLOW down your server due to all the calls to produce a disked cached copy of the page. Obviously, you can do some other mem caching with mysql that lesson the hit of mysql, but in the end, there is only so much you can do.