Posted 12 May 2012 - 04:04 PM
I'm glad to be able to contribute to this site and give a little something back to support your hard work. Thousands of people owe you so much for all the joy we get from it, for you making this site happen and keeping it running, and I hope many more will join in and make this fundraiser go through the roof
Posted 12 May 2012 - 05:27 PM
Your comments make sense, of course. I hope I wasn't coming off as a complainer (the board doesn't work! boo hoo!) when the truth is quite the opposite. Just reiterating that many of us - and I'm probably again overstepping my bounds by speaking for the board - would gladly contribute more to keep the board running smoothly. But yes, it makes sense to explore options that don't cost anything first.
Posted 12 May 2012 - 06:10 PM
No worries, we understand that people are just eager to get it working as well as possible. We're certainly very grateful for all the support and are very happy to see that the site means so much to so many.
Posted 13 May 2012 - 04:37 PM
Edit: Wow almost 125%
Edited by mor2, 13 May 2012 - 04:40 PM.
Posted 13 May 2012 - 04:42 PM
Posted 13 May 2012 - 07:51 PM
In general, the performance under the new setup has been really good as it is, especially compared to the old and much more standard LAMP (Linux, Apache, MySQL, PHP) stack we had been using. The problem is just that the new setup is so complicated that if one thing goes wrong, well, we saw what happened last night. So introducing one more element to the formula right during the heaviest load is, uh, let's just go with "probably unwise."
As an illustration, last night's fun adventure was caused by malformed requests to the wiki by some bot... the malformed requests caused PHP-FPM to spit out errors so rapidly that it was generating gigabytes of logfiles. And PHP-FPM will go into a weird error state if its error log is over 2GB, where it simply silently errors out on three out of every four requests or so. That was... fun. An upgrade to our PHP-FPM setup got us a patch that fixed the initial issue, and blowing away the enormous amount of random error logs that PHP-FPM had vomited all over the system fixed the rest, but tracking the issue down was an exercise in forensic system administration.
Edited by Sparks, 13 May 2012 - 07:52 PM.
Posted 15 May 2012 - 07:25 AM
Posted 15 May 2012 - 11:35 AM
Posted 16 May 2012 - 08:54 AM