Opened 5 years ago

Closed 4 years ago

#14173 closed enhancement (worksforme)

chutney verify: verify in parallel, rather than one at a time (Tor load / performance testing)

Reported by: teor Owned by: nickm
Priority: Low Milestone:
Component: Core Tor/Chutney Version:
Severity: Keywords: tor-perf SponsorR SponsorS tor-hs tor-client tor-bridge
Cc: nickm, dgoulet Actual Points:
Parent ID: #14175 Points:
Reviewer: Sponsor:

Description

There is a need to load-test Tor relays when bringing them up, and to performance-test tor in general, whether relaying or hidden services.

See:
Tor BSD Underperformance https://lists.torproject.org/pipermail/tor-dev/2015-January/008048.html
Simulate high Tor load https://lists.torproject.org/pipermail/tor-relays/2015-January/006203.html

It would be nice if chutney verify connections were done in parallel, but I don't think that's the case.

Nick, is this SponsorR, or SponsorS, or both?

Child Tickets

Change History (7)

comment:1 Changed 5 years ago by teor

Type: defectenhancement

comment:2 Changed 5 years ago by teor

Keywords: tor-client tor-bridge added

comment:3 Changed 5 years ago by teor

Parent ID: #14175

comment:4 Changed 5 years ago by teor

Keywords: SponsorR SponsorS added

Tagged with appropriate sponsors per nickm in #14174

comment:5 Changed 5 years ago by arma

Summary: chutnety verify: verify in parallel, rather than one at a time (Tor load / performance testing)chutney verify: verify in parallel, rather than one at a time (Tor load / performance testing)

comment:6 Changed 4 years ago by teor

Priority: normalminor

This might be incompatible with #14175, unless we make them separate commands.
Also, is this even important?
It might be if we have a 100+ node chutney network.

comment:7 Changed 4 years ago by teor

Resolution: worksforme
Status: newclosed

chutney already verifies in parallel, it's just that we don't send enough data to make it obvious.

Note: See TracTickets for help on using tickets.