3 ms·
"I ran a webmail service with 2m users that forked and exec'd a CGI for every request" Yes, but that met expectations of that time period, and expectations for
by tyingq 5y ago
"I ran a webmail service with 2m users that forked and exec'd a CGI for every request"
Yes, but that met expectations of that time period, and expectations for a webmail service. I'm curious if you also forked for every static asset...that's what this setup appears to do.
I just don't see the benefit of mysql choosing to use this today. It works, but there are other minimal http servers that would be just as simple, but would be faster and use fewer resources. I suppose they don't need to change it, but it's not really a great example of anything other than "fork is cheap on linux" to me.
- vidarh 5y agoPerformance expectations were if anything for the most part tighter than what people tend to get away with today. People hadn't gotten used to slow dynamic sites yet. We didn't fork for for every static asset, but the vast majority of overall requests were dynamic past the initial pageload, so the vast majority of requests resulted in fork. In terms of benefits, the simplicity is attractive. It's an approach that is in general quite resilient to errors.
- jjav 5y ago> Yes, but that met expectations of that time period, As peer poster said, expectations years ago were higher than today. It is frustrating how common it is for sites to think that downloading multiple MB of code just to show a simple page and having it take seconds to render is somehow ok. The expectations used to be ~100ms for a page load and render back when I was working on high performance web servers (~15 years ago).