cgi-bin

This is a followup to Gold's previous post that served 200 million requests per day with CGI, which Simon Willison wrote a post about, which we had a thread about three days ago at https://news.ycombinator.com/item?id=44476716. It addresses some of the misconceptions that were common in that thread. Summary: - 60 virtual AMD Genoa CPUs with 240 GB (!!!) of RAM - bash guestbook CGI: 40 requests per second (and a warning not to do such a thing) - Perl guestbook CGI: 500 requests per second - JS (Node) guestbook CGI: 600 requests per second - Python guestbook CGI: 700 requests per second - Golang guestbook CGI: 3400 requests per second - Rust guestbook CGI: 5700 requests per second - C guestbook CGI: 5800 requests per second https://github.com/Jacob2161/cgi-bin I wonder if the gohttpd web server he was using was actually the bottleneck for

I really like the code that accompanies this as an example of how to build the same SQLite powered guestbook across Bash, Python, Perl, Rust, Go, JavaScript and C: https://github.com/Jacob2161/cgi-bin

In the post I also showed results for a little `gohttpd` program running the CGI program: https://github.com/Jacob2161/cgi-bin/blob/main/gohttpd/main.... See as "Benchmarking (writes|reads) using Go net/http" It was faster but not by very much. Running CGI programs is just forking processes, so Apache's forking model works just about as well as anything else.