[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #31524 [Core Tor/Tor]: GETINFO bw-event-cache spike value(s) in it
#31524: GETINFO bw-event-cache spike value(s) in it
--------------------------------------+------------------------------------
Reporter: toralf | Owner: teor
Type: defect | Status: assigned
Priority: Medium | Milestone: Tor: 0.4.2.x-final
Component: Core Tor/Tor | Version: Tor: 0.4.1.4-rc
Severity: Normal | Resolution:
Keywords: 042-should, security-low | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+------------------------------------
Comment (by toralf):
Replying to [comment:6 nickm]:
> Replying to [comment:5 arma]:
> > I always figured this was from Tor starting up and seeding itself with
its previous self-measured bandwidth value from the state file, and
essentially thinking of itself as having done it all at once just then.
>
> Let's see if that looks like the case. Toralf, does the spike
correspond to a time in your logs when you restarted Tor?
This could indeed be the case. The issue is not seen immediately after
restarting the Tor process, after a while I do have a spike of 100 MB,
after a little bit longer while I do have the 3 GB.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31524#comment:7>
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