i've got an exit node that is doing a fair bit of bandwidth, but I think it is CPU bound at this point because I am getting these:
Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option
i'm wondering what I should set the MaxAdvertisedBandwidth to if I am averaging this type of traffic: http://torstatus.blutmagie.de/router_detail.php?FP=131b60b9afe6aea60042132d6...
it seems from the graphs, there are some clear plateaus at around 5100000, but I figured that folks here might have some suggestions that are better than just setting MaxAdvertisedBandwidth just to that number
thanks! micah
Maybe you're bottlenecked on DNS resolution?
On 05/24/2012 01:13 PM, micah anderson wrote:
i've got an exit node that is doing a fair bit of bandwidth, but I think it is CPU bound at this point because I am getting these:
Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option
i'm wondering what I should set the MaxAdvertisedBandwidth to if I am averaging this type of traffic: http://torstatus.blutmagie.de/router_detail.php?FP=131b60b9afe6aea60042132d6...
it seems from the graphs, there are some clear plateaus at around 5100000, but I figured that folks here might have some suggestions that are better than just setting MaxAdvertisedBandwidth just to that number
thanks! micah
* Steve Snyder swsnyder@snydernet.net wrote:
Maybe you're bottlenecked on DNS resolution?
Interesting, that's news to me. When I was operating an exit node I remember such log entries popped up on a regular basis. I also thought the CPU was the bottleneck, but still tried tweaking things; a rather unsuccessful quest. It just never occured to me DNS might be an issue.
Do you have a link to further read up on things? Is this a FAQ by now? And what's the solution; running a local caching nameserver? Thanks.
When I was operating an exit node...
Maybe I mis-read your original post, but I thought you *were* running an exit node. That's really the only scenario that requires a lot of name resolutions. An entry or middle nodes doesn't need much DNS traffic because they are only passing along packets.
An exit node with a lot of connections needs lots of name resolutions, making fast DNS a necessity. Whether that's accomplished with a local caching name server or some nearby name server depends on the resources you have available to you.
On 05/26/2012 11:20 AM, markus reichelt wrote:
- Steve Snyderswsnyder@snydernet.net wrote:
Maybe you're bottlenecked on DNS resolution?
Interesting, that's news to me. When I was operating an exit node I remember such log entries popped up on a regular basis. I also thought the CPU was the bottleneck, but still tried tweaking things; a rather unsuccessful quest. It just never occured to me DNS might be an issue.
Do you have a link to further read up on things? Is this a FAQ by now? And what's the solution; running a local caching nameserver? Thanks.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
markus reichelt -
micah anderson -
Steve Snyder