FWIW I also run in server mode constantly because its easy. My users (there are 10, they probably hit the server in bursts of 10 times one one day of the week) occasionally notice slowdowns and ping me. This is for an internal site only, no public facing, so shouldn't be huge numbers of users.
I restart the server and all is well. I don't see this as a problem since I know I should be running a 'real' server, but *shrug* this is good enough and a simple restart works well. Tomek ________________________________ From: fossil-users <[email protected]> on behalf of [email protected] <[email protected]> Sent: Friday, December 22, 2017 12:41 PM To: [email protected] Subject: fossil-users Digest, Vol 119, Issue 49 In message <CALwJ=mwtkrmysux-0h_kcfkouhwwdpwkogchd_bahbm+0m_...@mail.gmail.com> , Richard Hipp writes: >Maybe there is some kind of issue in the HTTP server implementation in >cgi.c that causes it to slow down after running for a long time. This >might have gone unnoticed, since (afaik) nobody uses "fossil server" >for long-running websites. I have fossil running in server mode for months at a time. I have never seen a a slowdown. Fossil is not directly internet facing though. I proxy through hiawatha. Also I only run http to the fossil server not HTTPS. Not sure if running behind a proxy and using http only could be factors. --
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
