3 ms·
we had to way overprovision to handle even momentary spikes in availability from any backing store. we aimed to run at around 20% unicorn worker utilization un
by spimmy 11y ago
we had to way overprovision to handle even momentary spikes in availability from any backing store. we aimed to run at around 20% unicorn worker utilization under normal conditions.
- railsfailsagaid 11y agoLol - rails performance fails again. Still, all the magic and security holes were worth it, right? And no with Google's go - the language so hipster it don't need no stinking generics, or proper error handling, life will be awesome?
- twelvenmonkeys 11y agoBut doesn't this sound less about over provisioning and more about optimizing the code you already had?
- spimmy 11y agooptimizing won't help you here, unfortunately. the process-per-request model is fundamentally flawed past a certain scaling point.