100 karma · joined November 26, 2010
Second of all, people should man up, step up from their lazy ass and move on. If the code is so really hard to refactor, maybe that code sucks really hard in the first place. I've seen incredible piles of garbage PHP code just to keep PHP 4 compatibility. It's 20-fu-11. 5 years since PHP 4 is officially dead. Maybe, just maybe, the internals team is not to blame for this stuff. I'm not even mentioning sentences containing the word "security" that seems to be some really scary stuff for some pumpkins still trying to figure out how SQLi works.
> SO_SNDBUF: [...] The default value is set by the wmem_default sysctl and the maximum allowed value is set by the wmem_max sysctl.
You can't use sysctl under OpenVZ. QED.
Moving forward to the actual issue. Something is really broken into your configuration. The first thing is the file AIO. But this is Linux's fault. The file AIO is broken by design. It bypasses the kernel file cache. Which is a pretty large performance hit per se. The second thing is the fact that I can easily get 55k req/s on a Q9400 with nginx, without even touching the sysctl parameters of a Ubuntu 10.04 x86_64. The only actual difference is nginx 1.0.x instead of the ancient 0.7.x you would actually find into the standard repos aka the production version I publish into my company's private repo.
I tried to use Quercus, but besides templating, it pretty much blows at everything else PHP related. http://www.caucho.com/resin-3.0/quercus/
Therefore this isn't a sole feature of the J-something language implementation on top of JVM.
Edit: removed the XSS, but here's the vector (if HN allows: input"><script>alert(String.fromCharCode(88,83,83))</script>)
PS: at least nginx takes care of this issue http://wiki.nginx.org/HttpCoreModule#msie_padding
OSX: http://www.mozilla.com/products/download.html?product=firefo...
Win: http://www.mozilla.com/products/download.html?product=firefo...
Linux: http://www.mozilla.com/products/download.html?product=firefo...
However, they're the same as RC2 (sha1sum confirms). Not uncommon though for Mozilla to release a RC as stable version without any modifications besides the version bump.
4chan.org vs ycombinator.com - that was a long fight. 4chan.org ended up being on top :)
However, this one has some points: http://www.blameitonthevoices.com/2009/03/great-debate.html
Proxmox ran inside a VirtualBox instance. All the allocated memory to the virtual machine was taken by the exploit. Even more, after rebooting the VirtualBox machine, it leaked the whole memory used by the affected Proxmox. The only way I could get it back was to stop the VirtualBox machine.