On Fri, 5 Apr 2013 13:50:29 -0400 Owen Gunden <ogunden@xxxxxxxxxx> allegedly wrote: > I have been running a non-exit tor relay for a few months now. It's > on a metered VPS, so after some experimenting I found that I can > afford about this much bandwidth: > > RelayBandwidthRate 250 KB > RelayBandwidthBurst 500 KB Owen You don't give details of your VPS, so comparisons may be difficult. But I have the following config options on my main (non-exit) relay: -------------- NumCPU 1 MaxOnionsPending 300 # rate limit - anything above about 2500 KB seems to cause tor # to invoke oom-killer BandwidthRate 2100 KB BandwidthBurst 2200 KB --------------- That relay is on a VM with 512Mb RAM, one CPU slice and 1Gig network connectivity (with unlimited traffic allowance). Stats can be seen at: https://atlas.torproject.org/#details/C332113DF99E367E4190424CE825057D91337ADD I had the same problems you are seeing until I set the rate limits above and increased MaxOnionsPending to 300. My CPU usage now hovers around 65-85% for about 2000 established tor connections. Mick --------------------------------------------------------------------- blog: baldric.net gpg fingerprint: FC23 3338 F664 5E66 876B 72C0 0A1F E60B 5BAD D312 ---------------------------------------------------------------------
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays