[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30733 [Core Tor/sbws]: sbws does not detect changes in descriptor bandwidth values
#30733: sbws does not detect changes in descriptor bandwidth values
-----------------------------------+-----------------------------------
Reporter: starlight | Owner: juga
Type: defect | Status: needs_revision
Priority: Very High | Milestone: sbws: 1.1.x-final
Component: Core Tor/sbws | Version: sbws: 1.1.0
Severity: Critical | Resolution:
Keywords: sbws-majority-blocker | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-----------------------------------+-----------------------------------
Comment (by starlight):
in longclaw data between 20190615-05 and 20190617-05 only 11% of relay
descriptor tuples match exactly--dramatic improvement, the change appears
to correct the issue
-----
my suggestion regarding sourcing descriptors from a relay tor instance
rather than client-only instance was intended for longer term (unless the
parameter change didn't work) -- the thought is dir-serve relay mode must
always maintain a complete set of current descriptors and is less likely
to regress than client modes; or sourcing from authorities has the
advantage of obtaining descriptors with no propagation delay
documentation on DirCache is confusing, seems to imply relation to dir-
server readiness where it really relates to minimizing client memory
utilization on very small hardware; what matters is FetchDirInfoEarly=1
FetchUselessDescriptors=1 are in effect activated by relay mode operation
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30733#comment:27>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs