I'd suggest putting up nginx as a reverse proxy to Apache. I had a situation sort of like this; under heavy load, Apache would have issues with semaphores that was hard to deal with. (Someone had handled the OOM-killing with a watchdog to respawn it.) For a large number of concurrent connections, nginx was much better, though that may have been due to the old MPM we were using - each connection tied up dozens of megs of memory in Apache, but maybe the request size-worth in nginx.
In the comment thread to another post of his on this issue, someone asked him why he didn't just use nginx, and he replied something along the lines of "because then I would need to learn nginx".
There's a long term plan to switch the wiki to being hosted on Emacs/Elnode. People could help out, especially with corner cases of the rendering. The repo is: https://github.com/aidalgol/elwiki
Note that we don't expect to do this quickly. Maybe we could get it up as a readonly mirror quite quickly.
Right now the issue is getting enough of the wiki cached that we're not under siege.
10 comments
[ 2.4 ms ] story [ 34.7 ms ] thread(Also a website that loads would be useful. ;) )
EmacsWiki isn't loading either.
Note that we don't expect to do this quickly. Maybe we could get it up as a readonly mirror quite quickly.
Right now the issue is getting enough of the wiki cached that we're not under siege.