Compile server, interesting concept. If no one cares to implement it, that means performance is not a high value item for people to improve upon. That's an in

Compile server, interesting concept. If no one cares to implement it, that means performance is not a high value item for people to improve upon. That's an interesting problem in doing a lot of lookup from main memory since the data structures are too big to fit in L1/L2. But that usage is not allocating a lot of short lived objects and freeing them, and reusing the freed memory right the way for next allocations. That's what Linus arguing for to reused the L1/L2 for the short lived objects, and thus GC is inappropriate. I would imagine compilers typically allocate objects that have long lifetime, such as declarations that have scope through the whole compile cycle. Also if memory allocation/deallocation is really a performance problem, then don't deallocate, just reuse the buffers. Reusing the same set of buffers would make sure they are hot in L1/L2. Anyway it has been an interesting discussion.