Opened 8 years ago

Closed 8 years ago

#3604 closed task (fixed)

Relay Node refresh causes heavy resource usage

Reported by: cypherpunks Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version:
Severity: Keywords: Vidalia Resource Usage, networkmap
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When tor is refreshing its relay node list, it seems to require a large amount of resources in doing so. It is speculated that this may be an issue with interacting with Vidalia when doing the refresh.

Child Tickets

Change History (7)

comment:1 Changed 8 years ago by arma

I think it's some combination of a) tor takes a little while to answer each getinfo request, and it adds up, and b) perhaps vidalia is not doing the optimal set (or ordering) of getinfo requests.

comment:2 Changed 8 years ago by Sebastian

Vidalia should probably be less zealous about learning all geoip info as quickly as possible, and do some other stuff inbetween

comment:3 Changed 8 years ago by arma

Would it be useful for Tor to learn a "tell me the geoip info of all the relays" getinfo, rather than requiring Vidalia to ask "what about this one? what about this one?" 2700 times?

comment:4 Changed 8 years ago by Sebastian

Hrm. Maybe. That would be a huge response. Maybe a better idea would be to say "give me the n relays from the mth segment of all relays ordered by fingerprint" or something, so vidalia can request 100 at a time or so and move through until it has all of them, and then fetch any that might still be missing

comment:5 in reply to:  3 Changed 8 years ago by joergent

Replying to arma:

Would it be useful for Tor to learn a "tell me the geoip info of all the relays" getinfo, rather than requiring Vidalia to ask "what about this one? what about this one?" 2700 times?

This would definitely speedup the start of Vidalia which is now lasting 5 minutes for our remote tor relay.

comment:6 Changed 8 years ago by chiiph

Keywords: networkmap added

I've taken care of this load/reload routers issue in my branch chiiph/featNetworkMap. It will be out with 0.3.2-alpha.

As for having all geoip together would be a huge response, we already have something similar with getinfo ns/all, would it be worse than that?

comment:7 Changed 8 years ago by chiiph

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.