2 ms·
Where this hair gets particularly thin is when you start with an app that uses fixed memory and then you end up in a situation where it works out that running m
by hinkley 4y ago
Where this hair gets particularly thin is when you start with an app that uses fixed memory and then you end up in a situation where it works out that running many copies of the code is a solution to a (scalability) problem. Then pre-allocation becomes a problem because you've just locked up a hefty chunk of memory.
And that can be a self fulfilling prophecy. One of the problems with memory pools is concurrent access, both by your programming language and the processor, and so it starts looking attractive to spool up a process per task.