4 ms·
you now containers are just processes, right? This is what they did, but because they didn't need to schedule other jobs on the same machine, kubernetes or eve
by motoboi 5y ago
you now containers are just processes, right?
This is what they did, but because they didn't need to schedule other jobs on the same machine, kubernetes or even docker would be overkill.
In this case, simple VM orchestration seems like a fine solution.
- PaywallBuster 5y agoIndeed, but you wouldn't be thinking about instance sizes, how many processes per instance and wondering if you're hitting kernel limits with all the issues coming up
- motoboi 5y agoWhy not?
- zbentley 5y agoYou'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.
- PaywallBuster 5y agoThat's what they're doing now. One app pool with one worker x number of cores
- zbentley 5y agoI assumed they're managing all those workers under one parent process which compiled their codebase on start. Perhaps that assumption was in error.