On Jun 2, 2015, at 12:21 PM, Richard Hipp <[email protected]> wrote: > > On 6/2/15, Philip Bennefall <[email protected]> wrote: >> after the Fossil standalone server has been >> running for quite some time it becomes terribly sluggish. ... I am >> running on a lower end Linode VPS, but so is the sqLite repository as >> far as I know and I have never had any trouble with that over the four >> years I've been following it. >> > > The difference is probably that the https://www.sqlite.org/src site is > running fossil using CGI, not as a stand-alone server.
You’re thinking some kind of memory leak, then? [*] That should be easy for the OP to [dis]prove, such as via top(1). For reference, my local instance is taking 0.0% of memory after running for a couple of weeks. (Meaning < ~200 MiB, given that there is 6 GiB of physical RAM + 16 GiB of swap configured on this machine.) [*] I don’t mean to accuse SQLite or Fossil of completely losing track of allocated memory, but if it’s allocating chunks of memory that don’t get properly freed until the program exits, it amounts to the same thing. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
