mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2025-02-25 07:07:52 +01:00
33a0c619a8
There are three reasons we use a cached_dir_t to hold a consensus:
1. to serve that consensus to a client
2. to apply a consensus diff to an existing consensus
3. to send the consensus to a controller.
But case 1 is dircache-only. Case 2 and case 3 both fall back to
networkstatus_read_cached_consensus(). So there's no reason for us
to store this as a client. Avoiding this saves about 23% of our RAM
usage, according to our experiments last month.
This is, semantically, a partial revert of
|
||
|---|---|---|
| .. | ||
| app | ||
| config | ||
| core | ||
| ext | ||
| feature | ||
| lib | ||
| rust | ||
| test | ||
| tools | ||
| trunnel | ||
| win32 | ||
| include.am | ||