On 24 Jun (01:49:18), starlight.2018q2@xxxxxxxxxxx wrote: > Hi, > > No leaks. The VM has 1GB, very light for moderate busy relay. > > Should be 4GB, perhaps 3DB would do. Settings should include: > > AvoidDiskWrites 1 > DisableAllSwap 1 > MaxMemInQueues 1024MB # perhaps 1536MB > > My relays run about 800MB to 1.2GB. A nice way to view memory > usage is with > > egrep '^Vm' /proc/$(cat /var/run/tor.pid)/status > > which might show something like > > VmPeak: 871696 kB > VmSize: 710152 kB > VmLck: 710148 kB > VmHWM: 810872 kB > VmRSS: 649328 kB > VmData: 492052 kB > VmStk: 93 kB > VmExe: 4704 kB > VmLib: 104724 kB > VmPTE: 1044 kB > > Notice that current VmSize usage is less than VmPeak, > indicating that memory was release by glibc malloc. > > Tor consumes substantial skbuf memory in the kernel, which > accounts for some of the difference in reported size for > VmRSS and VmSize and total memory consumption. What OS is this running on? Can you possibly send back a SIGUSR1 log? Kernel memory leak means we are buffer bloating it with cells... which we aren't suppose to do these days :S ... Thanks! David -- mtl83aVORGbFMy0uOJnLcNQG64cDwnBUp5hK73imIrw=
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays