Y
Hacker News
new
|
ask
|
show
|
jobs
by
zbentley
1763 days ago
You'd probably be worrying
more
about instance sizes if you ran a single executor per container; the memory overhead of your app would become a problem very quickly unless it's startup footprint was quite small.
1 comments
PaywallBuster
1762 days ago
That's what they're doing now.
One app pool with one worker x number of cores
link
zbentley
1761 days ago
I assumed they're managing all those workers under one parent process which compiled their codebase on start. Perhaps that assumption was in error.
link
One app pool with one worker x number of cores