Brief network maintenance

Posted by on Dec 9th, 2010, at 4:31 pm in Site Stuff.

We’re undergoing some server maintenance for the next few hours while we upgrade to a more sexy server; so be aware, dearest readers :).


Shadowized: you are officially on the new server, performance should be quite a bit better during primetime but I’m still tuning php/mysql to match the new server specs.

Feel free to post any comments about Brief network maintenance, including links to downloads, samples, screenshots, information, or any other relevant information. Please note that anything you download from here, you do so at your own risk. Remember if you see Trusted Poster, this means they are trusted commentors!

23 Comments about “Brief network maintenance”

  1. 1. Shadowized Trusted Poster Dec 9th, 2010 at 4:11 pm

    ok, and we’re officially all on the new server.

  2. 2. n/a Dec 9th, 2010 at 4:50 pm

    I demand pics.

  3. 3. bDk (┌∩┐(◣_◢)┌∩┐) Trusted Poster Dec 9th, 2010 at 4:52 pm

    nekkid ?

  4. 4. Shadowized Trusted Poster Dec 9th, 2010 at 5:10 pm

    baw, we lost a few comments but oh well, the responsiveness of the site should be a bit better since it will be harder to max the server out now.

    granted, we will eventually be forced to upgrade again down the road to a proper dual quadcore box with around 24gb ram, but for now this will do the job quite well.

    that poor old x3220 just couldn’t handle 2000 requests per second even with nginx / php-fpm ;(

  5. 5. n/a Dec 9th, 2010 at 5:29 pm


  6. 6. derp Dec 9th, 2010 at 5:29 pm


  7. 7. who? Dec 9th, 2010 at 6:40 pm

    lol. whos gonna pay for the server costs?

  8. 8. Shadowized Trusted Poster Dec 10th, 2010 at 3:51 am

    fixed timezone stupidity, everything should be good I think.

  9. 9. IceBear Dec 10th, 2010 at 8:38 am

    Thanks for all the work and sharing, before, after and into the future.

    Not being slammed with ads makes SceneSource a 2 or 3 times a day visit for me.
    (I gladly click on the sponsors for your support, just because we are not forced to…)

    Wishing all the staff and readers a safe and happy holiday season, and peace and health in the 2011!

  10. 10. buschwusch Dec 10th, 2010 at 1:02 pm


  11. 11. falk Dec 10th, 2010 at 2:18 pm

    Have you looked at Varnish? Helped quite alot on a heavy site I once worked on.

  12. 12. buschwusch Dec 10th, 2010 at 5:35 pm

    you could also check out
    i use it on my personal site, could really improve my performance for visitors in another continent.

  13. 13. Shadowized Trusted Poster Dec 10th, 2010 at 8:14 pm

    Varnish is probably the next thing on my to-do list.

  14. 14. jix Dec 10th, 2010 at 9:13 pm

    okay wait a minute… I never heard of cloudflare and varnish. cloudflare costs money and the video does not really convince me (distributing your site, wtf). varnish looks better at first glance, but setup seems to be a workout.

    srsly what about apc? apc needs like no setup at all and is quite the performance boost. also another thing that accelerates any website is memory sessions. you can either use apc as well or have your mysql table set to memory. since sessions are to be considered like any cache data, that is _volatile_, this is the way to go.

  15. 15. jix Dec 10th, 2010 at 9:13 pm

    also you should implement a combine engine that minifies your external javascript files, glues them togeter and finally puts them into the apc cache. when dealing with a lot of hits, this may save you some server load and boosts response times for every visitor.

  16. 16. jix._. Dec 10th, 2010 at 9:16 pm

    basically I suggest getting the highest score possible on yslow. almost everything on this list is important and trying to get a 100% score greatly improves overall performance. even simple things like adding fare future expires for images etc. may reduce server load quite noticeably!

    any objections…? 🙂

  17. 17. n/a Dec 10th, 2010 at 9:22 pm

    I still don’t see any pics.

  18. 18. Shadowized Trusted Poster Dec 10th, 2010 at 9:25 pm

    we already use apc, and we do minify the code being sent to people.

    I agree about cloudflare being pretty useless, at a glance I’ve done just about everything on there aside from the CDN.

  19. 19. jix Dec 10th, 2010 at 11:12 pm

    mint, sampleHover and commentFilter are not minified, but that’s not important 😉
    I suggest linking a single js.php as script tag that reads all js-files, glues them together in one big string, caches it via apc and delivers the content, therefore you save 6 requests to the server 🙂

    (i’ve seen that you already have a pretty good score on yslow…)

  20. 20. jix Dec 10th, 2010 at 11:14 pm

    question: why is it that so many times a write a comment, but it does not appear after submitting??

  21. 21. Shadowized Trusted Poster Dec 10th, 2010 at 11:50 pm

    probably spam filters being retarded, I’ll fix it for you.

    edit: should be ok now, something was broken in there, anyways… we don’t have an issue with static files, that’s all done up via nginx which can happily serve over 10000+ requests per second and not use more than 1-3% cpu.

    the problem itself is php and how much of a strain it puts on the server by having to constantly recompile the same php code, hence why something like varnish is good it would sit infront of nginx, which sits infront of php.

    it’s a crazy reverse proxy loop really, I mean at current this should keep things good for the time being, those “20 second to load a page” times were all due to the cpu being maxed out, but with this I’m not seeing it, it’s at least double the speed and if I mod the kernel a bit more I can probably squeeze out some more from it with preemption and make it play nicer while choking on itself.

  22. 22. jix Dec 11th, 2010 at 8:16 am

    thanks 🙂

    well yes that is in fact why i disapprove of scripting languages in general. without caching every page load requires opening all the scripts and parsing/interpeting them, then last but not least throwing everything away to do exactly the same thing again. what a load of crap really ^^
    but as you know apc stores compiled php code in its opcode hashmaps, which means any cached script virtually has no overhead anymore. so my opinion is you don’t need anything other than apc. if however you still have performance issues, you will have to focus on the programming itself. there is _always_ a way to improve performance programmatically, and wordpress itself is not the fastest application.

    if you can’t improve the programming or it needs to be that complex (wich rarely is the case). i would suggest facebook’s own hiphop engine which compiles your php code into c code. it might be somewhat similar to this varnish thing, but i would suggest these facebook guys really know what they are doing, since they deal with an unbelieveable huge amount of requests 😀

    but what one may also do is take every rendered page (e.g. articles) and before sending them to the user have it cached together with its url via db for example. then you hook another script to your index.php and see if there already is a cached version for the requested page.
    the only thing to really take care of is getting rid of the cached pages once e.g. a commment is added.
    and that is in fact what i would to. scripted applications need caching due to their poor performance. custom building your own cache surely is the best and most fun thing to do 🙂

  23. 23. falk Dec 11th, 2010 at 11:27 am

    What about the database? Perhaps wp is doing some weird queries. Analyze the slow query log with maatkit or similar.