[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #29427 [Core Tor/Tor]: kist: Poor performance with a small amount of sockets
#29427: kist: Poor performance with a small amount of sockets
-------------------------------------------------+-------------------------
Reporter: dgoulet | Owner: dgoulet
Type: defect | Status:
| needs_review
Priority: Medium | Milestone: Tor:
| 0.4.2.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.2.1-alpha
Severity: Major | Resolution:
Keywords: tor-sched, kist, regression?, | Actual Points: 0.1
041-deferred-20190530, 042-should, |
BugSmashFund |
Parent ID: | Points: 0.1
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by dgoulet):
Replying to [comment:13 nickm]:
> >We do not. The choice for the interval is based on torrc and consensus
so it shouldn't matter on which platform?
>
> My concern is that different platforms sometimes handle small timers
very differently.
True. For multiple platforms, I have to say no :S.
Timers at the msec level I would assume would be fine on most of our
targeted platforms. Also, this specific interval is only used on Linux and
BSD. Windows uses Vanilla scheduler which doesn't have this problem.
> Should there be separate consensus parameters for client and server?
Yes this is a good idea actually. But this means 043 considering past our
feature freeze?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29427#comment:14>
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