News for hackers. Stuff that matters.

A comment on X86 Register Encoding. Parent comment

Re:X86 Register Encoding by bertr4nd on Tuesday November 01, 2016 @05:21PM (#12850131)
HHVM's register allocator has a few tricks to minimize code size. Among other things it tends to prefer the old regs to the new x64 ones. As you might imagine code size is a significant challenge for Facebook so these kind of optimizations tended to give nice wins.
[ Parent | on HN ]
Re:X86 Register Encoding by munificent on Tuesday November 01, 2016 @05:47PM (#12850320)
> As you might imagine code size is a significant challenge for Facebook

Maybe I'm missing something obvious, but why is code size a big concern for Facebook's server code?

[ Parent | on HN ]
Re:X86 Register Encoding by twic on Tuesday November 01, 2016 @06:14PM (#12850574)
"Because Facebook's entire code base is compiled down to a single binary executable, the company's deployment process is quite different from what you'd normally expect in a PHP environment. Rossi told me that the binary, which represents the entire Facebook application, is approximately 1.5GB in size."

http://arstechnica.com/business/2012/04/exclusive-a-behind-t...

[ Parent | on HN ]
Re:X86 Register Encoding by bertr4nd on Tuesday November 01, 2016 @08:11PM (#12851286)
It's not compiled ahead of time any more, but yeah, that gives you an idea of just how darn big the server side code is.
[ Parent | on HN ]