Thanks Logforme - yeah I was trying that before I sent the first email in this chain, but maybe I didn't go low enough with the advertised bandwidth. When the 0.2.4 compilation is done (it's still chugging along) I'll try going lower and see if it helps.ChrisOn 14 October 2013 21:38, Logforme <m7527@xxxxxx> wrote:
On 2013-10-14 22:01, Chris Whittleston wrote:Only option that I know of is to reduce the bandwidth you advertise to
> I see - so I'll probably still see the problem with a huge number of
> circuits being created after I've finished building 0.2.4. Is there
> any way to limit this, I'm guessing reducing the bandwidth wouldn't
> actually help? I guess I'll look into how much further I can overclock
> the CPU...
the network. The more bandwidth you advertise the more circuits the tor
network will throw at your relay. The following flags in the torrc file
can be used (with my current understanding of them):
BandwidthRate : The max bandwidth you provide over a long period of time
BandwidthBurst : The max bandwidth you provide over a short period of time
MaxAdvertisedBandwidth : The max bandwidth you tell the tor network about
So you can set BandwidthRate to the real max you want to provide and
then set MaxAdvertisedBandwidth to a number low enough to prevent
circuit overload.
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
--
Dr Chris WhittlestonÂæä
Department of Chemistry
University of Cambridge
Lensfield Road, Cambridge, CB2 1EW
Email: csw34@xxxxxxxxx
Tel: +44 (0)1223 336423
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays