On 13 August 2013 13:06, Stephan Beal <sgb...@googlemail.com> wrote: > Didn't think of that, actually. But the fact that fossil forks a new process > by itself for each request eliminates the benefit of fastcgi (which is > primarily to reduce the forks by re-using the same app instance).
But those forks (on any modern Unix/Mac) of a running, initialised fossil will be pretty cheap using copy-on-write for the pages, versus forks+execs+startup for traditional CGI - should still be a significant win. ../Dave _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
