←back to thread

155 points feep | 1 comments | | HN request time: 0.202s | source
Show context
sugarpimpdorsey ◴[] No.44464798[source]
Surprised with the choice of Apache. There are better choices for serving CGI nowadays. The only reason for still running Apache is you have legacy cruft that requires Apache (like .htaccess).
replies(5): >>44464841 #>>44464842 #>>44465210 #>>44466147 #>>44469039 #
1. jacob2161 ◴[] No.44466147[source]
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.