[tor-bugs] #24737 [Core Tor/Tor]: oft given MaxMemInQueues advice is wrong

Tor Bug Tracker & Wiki blackhole at torproject.org
Sun Dec 31 21:31:46 UTC 2017


#24737: oft given MaxMemInQueues advice is wrong
----------------------------+----------------------------------
 Reporter:  starlight       |          Owner:  (none)
     Type:  defect          |         Status:  new
 Priority:  Medium          |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor    |        Version:
 Severity:  Normal          |     Resolution:
 Keywords:  doc, tor-relay  |  Actual Points:
Parent ID:                  |         Points:
 Reviewer:                  |        Sponsor:
----------------------------+----------------------------------

Comment (by starlight):

 have to add:

 1) the observation that `tor` worst-case memory consumption is 2x
 `MaxMemInQueues` does not include kernel socket-buffer memory consumption;
 socket memory can be substantial and must be allowed for, which is where I
 came up with setting MaxMemInQueues to 40% of free memory available for a
 given instance; note KIST lowers egress socket buffering, but leave
 ingress socket memory utilization to the kernel and to the behavior of
 remote peers

 2) inspiration for this ticket was the OOM kill of a daemon configured
 MaxMemInQueues=2G running on 4G machine, and subsequently the event
 mentioned in "Description" -- both apparently were "sniper attacks"

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24737#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list