Re:We at $Famous_company switched to $Hyped_technology
by JJMcJ on Monday May 11, 2020 @05:10PM
(#23147117)
One advantage of CGI is that the worker process terminates, and all the resources get freed.
Not that I recommend CGI for anything but very low usage sites, typically internal ones with a fixed user base.
Re:We at $Famous_company switched to $Hyped_technology
by hinkley on Monday May 11, 2020 @06:36PM
(#23147967)
Not to worry. We'll cloud-enable fastcgi and call it Serverless.
Re:We at $Famous_company switched to $Hyped_technology
by redis_mlc on Tuesday May 12, 2020 @01:17AM
(#23150788)
eBay did the scheduled reboot thing around 2000, but on a massive scale.
Their front-end servers were Windows ISAPI, and leaked memory like a sieve. So there was a documented process for rebooting groups of servers with a diagram dividing the front-end servers into rebootable clusters and the time between reboot intervals.
And yes, docker/k8s sure reminds me of those days when reviewing logs today and seeing some pods with unexplained non-zero restart counts.
Source: worked there, read the documentation.
The servers were stable for a day or two, so they cooked up a reaper process that would sequentially reboot every machine in the cluster, wait for it to start routing traffic, then reboot the next one. Every machine got at least one reboot a day from this.
The moral authority with which I used to share that anecdote has eroded quite a bit in the years of Continuous Deployment. Most of my endpoints reboot at least once a week, except for holidays where we occasionally discover longevity bugs. With autoscaling some instances will be up for hours at a time (and if we are not very careful we'll completely pollute our server statistics).