Thus said Philip Bennefall on Wed, 15 Jul 2015 20:22:07 +0200: > About a month ago I reported having some issues with the standalone > Fossil server, where it would slow down significantly after running > for an extended period.
What specifically is slow? Clone? Sync? Accessing pages served by the standalone Fossil server? All of these are network related, so what happens if you do the same things locally on the server to eliminate network slowness? For example, if clone is slow, login to the server and just clone locally: fossil clone http://server.blastbay.com/blastmidi/ /tmp/bmclone.fossil > http://server.blastbay.com/blastmidi/ This one doesn't seem slow for me. I cloned it in 1 second. Browsing the site also seems fairly responsive. > Now, I am in a position to gather any information that the developers > might need. However I am new to Linux and have no idea what > information might be of use, ... The things to look for are: How much memory the process is using. You can use ps for that. How much cpu is the process using. Again perhaps top. Has the process been reniced? If so, this means it will run with a lower priority than other processes and may respond slowly due to this. What journal mode do you have enabled on your Fossils? Also, since fossil server spawns a new process for each new connection, it might be hard to diagnose if the problem isn't necessarily with the server, but the forked server handler. Another thing to look at is how many file descriptors the process has open. With linux I believe you can use lsof to obtain this information (or /proc/PID/fd). You could use strace to profile where the process is going with syscalls and things. Might want to use -f to follow children since a new connection will fork. How much free memory does your system have? The free command should help with this. How about disk space? How about inodes? What about contention for I/O resources? E.g. is there something else hammering your disks which also slows down Fossil? What about netstat output? Specifically netstat -na? Does it show a lot of connections to your Fossil port either ESTABLISHED or in any other state? Maybe fossil is unable to allocate a new port because you're being DDoSed? Andy -- TAI64 timestamp: 4000000055a732a3 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
