Hey Swagger,
This board isn't going to go through updates in August when we are all talking about summer practices, like the previously place, right?

Pretty big board with lots of people, assume decent amount of redundancies as well correct?

I hope I don't get this too often, either! "The maximum server load limit has been reached. Please check back later once the server is less busy."

I don't think GTS has any idea about the volume that JMU is going to bring to these boards. He is going to have to invest in new equipment.

I think the reason for the last overload message was because he was debugging. Usually when messages like that happen, we report it on this thread http://csnbbs.com/showthread.php?tid=626230

Colocated. Own the hardware.

Apache and MySQL are VERY finely tuned. Apache is running a FCGI socket that punts to FPM based PHP. This allows for pooled caching within PHP itself and removes virtually all apache overhead. Most of the apache box resources are chugging away at php-fpm. In fact apache is SO LOW in resource use I haven't even considered nginx. MySQL is using HugeTLB support and enormous InnoDB caches. We wouldn't be up now if stuff even occasionally hit disk. There is varnish running in front of Apache so I can now easily spin up cloud based apache nodes if it comes to it. I really don't want to cluster yet if I don't have to. I want to feel like I've really done everything possible to prevent that so that when I do scale I do as efficiently as possible. I've got a few options left ... nginx (doubt it will make much if any difference), delving into the slow areas of MyBB in PHP crunching (potentially VERY productive), and improving MyBB's ability to varnish cache for guests (potentially productive).

The next MyBB release has full 5.4 support, and I'm told the upgrade and switch PHP 5.4 will bring some more speed improvements as well.

Hardware is a 1U twin with each side having dual QC Xeons that are getting to be on the older side now ... Penryn (Core 2 Duo) era Harpertown 5400 series Xeons. Both have more RAM than they use. Both have RAID 1 Raptors.

The bottleneck right now is PHP's cpu demands.


There is an update coming out for the board software any day now that supports PHP 5.4 and purportedly should deliver some performance oomph.

The max load you just got was me turning on a profiler/debugger to examine how PHP is performing after I made some tweaks. It generated 120 MB of debug dumps in 20 seconds.



It is looking like I'll be upgrading the hardware before this coming football season. Hellooooooo $2-5K. And that's why we have Google ads. :)

Really wish AMD wasn't taking it on the chin with their crappy processors. The price premiums Intel wants in server land make even the US Congress blush. You can't touch an eight core Xeon for under $1,100 EACH anymore. Oof!

http://www.newegg.com/Product/ProductLis...rchInDesc=

(04-09-2013 08:48 AM)georgia_tech_swagger Wrote:  Colocated. Own the hardware.

Apache and MySQL are VERY finely tuned. Apache is running a FCGI socket that punts to FPM based PHP. This allows for pooled caching within PHP itself and removes virtually all apache overhead. Most of the apache box resources are chugging away at php-fpm. In fact apache is SO LOW in resource use I haven't even considered nginx. MySQL is using HugeTLB support and enormous InnoDB caches. We wouldn't be up now if stuff even occasionally hit disk. There is varnish running in front of Apache so I can now easily spin up cloud based apache nodes if it comes to it. I really don't want to cluster yet if I don't have to. I want to feel like I've really done everything possible to prevent that so that when I do scale I do as efficiently as possible. I've got a few options left ... nginx (doubt it will make much if any difference), delving into the slow areas of MyBB in PHP crunching (potentially VERY productive), and improving MyBB's ability to varnish cache for guests (potentially productive).

The next MyBB release has full 5.4 support, and I'm told the upgrade and switch PHP 5.4 will bring some more speed improvements as well.

Hardware is a 1U twin with each side having dual QC Xeons that are getting to be on the older side now ... Penryn (Core 2 Duo) era Harpertown 5400 series Xeons. Both have more RAM than they use. Both have RAID 1 Raptors.

The bottleneck right now is PHP's cpu demands.


There is an update coming out for the board software any day now that supports PHP 5.4 and purportedly should deliver some performance oomph.

The max load you just got was me turning on a profiler/debugger to examine how PHP is performing after I made some tweaks. It generated 120 MB of debug dumps in 20 seconds.



It is looking like I'll be upgrading the hardware before this coming football season. Hellooooooo $2-5K. And that's why we have Google ads. :)

My head just exploded. Glad you are at the controls, thanks for hosting us!

(04-09-2013 08:48 AM)georgia_tech_swagger Wrote:  Colocated. Own the hardware.

Apache and MySQL are VERY finely tuned. Apache is running a FCGI socket that punts to FPM based PHP. This allows for pooled caching within PHP itself and removes virtually all apache overhead. Most of the apache box resources are chugging away at php-fpm. In fact apache is SO LOW in resource use I haven't even considered nginx. MySQL is using HugeTLB support and enormous InnoDB caches. We wouldn't be up now if stuff even occasionally hit disk. There is varnish running in front of Apache so I can now easily spin up cloud based apache nodes if it comes to it. I really don't want to cluster yet if I don't have to. I want to feel like I've really done everything possible to prevent that so that when I do scale I do as efficiently as possible. I've got a few options left ... nginx (doubt it will make much if any difference), delving into the slow areas of MyBB in PHP crunching (potentially VERY productive), and improving MyBB's ability to varnish cache for guests (potentially productive).

The next MyBB release has full 5.4 support, and I'm told the upgrade and switch PHP 5.4 will bring some more speed improvements as well.

Hardware is a 1U twin with each side having dual QC Xeons that are getting to be on the older side now ... Penryn (Core 2 Duo) era Harpertown 5400 series Xeons. Both have more RAM than they use. Both have RAID 1 Raptors.

The bottleneck right now is PHP's cpu demands.


There is an update coming out for the board software any day now that supports PHP 5.4 and purportedly should deliver some performance oomph.

The max load you just got was me turning on a profiler/debugger to examine how PHP is performing after I made some tweaks. It generated 120 MB of debug dumps in 20 seconds.



It is looking like I'll be upgrading the hardware before this coming football season. Hellooooooo $2-5K. And that's why we have Google ads. :)

Well damn . . If i'd have known it was this easy I would have started my own board.

BTW my pressure release valve if it gets really bad is killing access for guests. But I won't do that unless it starts getting persistently on the edge.

(04-09-2013 08:48 AM)georgia_tech_swagger Wrote:  Colocated. Own the hardware.

Apache and MySQL are VERY finely tuned. Apache is running a FCGI socket that punts to FPM based PHP. This allows for pooled caching within PHP itself and removes virtually all apache overhead. Most of the apache box resources are chugging away at php-fpm. In fact apache is SO LOW in resource use I haven't even considered nginx. MySQL is using HugeTLB support and enormous InnoDB caches. We wouldn't be up now if stuff even occasionally hit disk. There is varnish running in front of Apache so I can now easily spin up cloud based apache nodes if it comes to it. I really don't want to cluster yet if I don't have to. I want to feel like I've really done everything possible to prevent that so that when I do scale I do as efficiently as possible. I've got a few options left ... nginx (doubt it will make much if any difference), delving into the slow areas of MyBB in PHP crunching (potentially VERY productive), and improving MyBB's ability to varnish cache for guests (potentially productive).

The next MyBB release has full 5.4 support, and I'm told the upgrade and switch PHP 5.4 will bring some more speed improvements as well.

Hardware is a 1U twin with each side having dual QC Xeons that are getting to be on the older side now ... Penryn (Core 2 Duo) era Harpertown 5400 series Xeons. Both have more RAM than they use. Both have RAID 1 Raptors.

The bottleneck right now is PHP's cpu demands.


There is an update coming out for the board software any day now that supports PHP 5.4 and purportedly should deliver some performance oomph.

The max load you just got was me turning on a profiler/debugger to examine how PHP is performing after I made some tweaks. It generated 120 MB of debug dumps in 20 seconds.



It is looking like I'll be upgrading the hardware before this coming football season. Hellooooooo $2-5K. And that's why we have Google ads. :)

So you've heard of the Millenium Falcon!?!

No offense to Zone Admin, but I feel we have a slightly more involved owner here!

Yea, I'm going to force all people who aren't logged in to hit a cached version of the pages they request. This should radically reduce the load.

Anddddd two hours of parsing that debug data and making tweaks and things are running nice and snappy again.

That is the power of Jim Donnan and his kung fu.

(04-09-2013 11:12 AM)georgia_tech_swagger Wrote:  Anddddd two hours of parsing that debug data and making tweaks and things are running nice and snappy again.

That is the power of Jim Donnan and his kung fu.

Mickey Matthews learned kung fu from Jim Donnan. Taught him how to punch 'em in the neck.

I don't know what a "quick Cincinnati" is, but I know it can't smell good.

(04-09-2013 11:18 AM)Pitz Wrote:  I don't know what a "quick Cincinnati" is, but I know it can't smell good.

I pushed a few hundred thousand ancient posts on the Cincinnati board into a new archival board. The weak spot of our board software is really big boards or threads that span years. They force the database to go over millions and millions of records to serve every request on them. So big ancient threads get killed when I notice they cause a problem, and boards with huge numbers of ancient posts get an archival purge when I notice they cause a problem. But I have to momentarily kill the board when I do it. The server doesn't like me if I try to move around a few million posts while 2,000+ people are using it.