Commit 8a38e18c authored by Hiro's avatar Hiro 🏄
Browse files

Make sentences 1 line

parent 83b42e23
......@@ -133,13 +133,10 @@ Let's find out what some of these lines actually mean:
When a relay starts seeing "dropped", it is a CPU/RAM problem usually.
Tor is sadly single threaded _except_ for when the "onion skins" are processed.
The "onion skins" are the cryptographic work that needs to be done on the famous
"onion layers" in every circuits.
The "onion skins" are the cryptographic work that needs to be done on the famous "onion layers" in every circuits.
When tor processes the layers we use a thread pool and outsource all of that work
to that pool.
It can happen that this pool starts dropping work due to memory or CPU pressure
and this will trigger an overload state.
When tor processes the layers we use a thread pool and outsource all of that work to that pool.
It can happen that this pool starts dropping work due to memory or CPU pressure and this will trigger an overload state.
If your server is running at capacity this will likely be triggered.
......@@ -147,12 +144,10 @@ If your server is running at capacity this will likely be triggered.
Any counter in the "*_dns_error_total" realm indicates a DNS problem.
DNS timeouts issues only apply to Exit nodes. If tor starts noticing DNS timeouts,
you'll get the overload flag. This might not be because your relay is overloaded
in terms of resources but it signals a problem on the network.
DNS timeouts issues only apply to Exit nodes. If tor starts noticing DNS timeouts, you'll get the overload flag. This might not be because your relay is overloaded in terms of resources but it signals a problem on the network.
DNS timeouts at the Exits are a _huge_ UX problem for tor users. Therefore Exit
operators really need to address these issues to help the network.
DNS timeouts at the Exits are a _huge_ UX problem for tor users.
Therefore Exit operators really need to address these issues to help the network.
```tor_relay_load_oom_bytes_total{...}```
......@@ -160,14 +155,10 @@ An Out-Of-Memory invocation indicates a RAM problem.
The relay might need more RAM or it is leaking memory.
If you noticed that the tor process is leaking memory, please report the issue via either [GitLab](https://gitlab.torproject.org) or send an email to the [tor-relays mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays).
Tor has its own OOM handler and it is invoked when 75%, of the total memory tor
thinks is available, is reached. Thus, let say tor thinks it can use 2GB in
total then at 1.5GB of memory usage, it will start freeing memory. That is
considered an overload state.
Tor has its own OOM handler and it is invoked when 75%, of the total memory tor thinks is available, is reached. Thus, let say tor thinks it can use 2GB in total then at 1.5GB of memory usage, it will start freeing memory.
That is considered an overload state.
To estimate the amount of memory it has available, when tor starts, it will use
MaxMemInQueues or, if not set, will look at the total RAM available on the system
and apply this algorithm:
To estimate the amount of memory it has available, when tor starts, it will use MaxMemInQueues or, if not set, will look at the total RAM available on the system and apply this algorithm:
```
if RAM >= 8GB {
memory = RAM * 40%
......@@ -180,15 +171,11 @@ and apply this algorithm:
memory = max(250MB, memory)
```
To avoid an overloaded state we recommend to run a relay above 2GB of RAM on
64bit. 4GB is advised, although of course it doesn't hurt to add more RAM if you
can.
To avoid an overloaded state we recommend to run a relay above 2GB of RAM on 64bit. 4GB is advised, although of course it doesn't hurt to add more RAM if you can.
One might notice that tor could be called by the OS OOM handler itself.
Because tor takes the total memory on the system when it starts, if the overall
system has many other applications running using RAM, it ends up eating too much
memory. In This case the OS could OOM tor without tor even noticing memory
pressure.
Because tor takes the total memory on the system when it starts, if the overall system has many other applications running using RAM, it ends up eating too much memory.
In This case the OS could OOM tor without tor even noticing memory pressure.
```
tor_relay_load_socket_total
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment