On 09/11/2013 07:20 PM, Jesse Victors wrote:
Hello everyone, newcomer here.
I'm behind very fast connection (11.5 MB/sec down, 7.5 MB/sec up) and I thought that the Tor network could benefit from my connection, especially since it's apparently been under high load recently. Per the latest blog posts, I downloaded the beta TBB and configured it as a relay under Linux. It's been up for almost two days now, yet it's still being utilized at a very, very small fraction of it's potential. In the network map, I see that my relay has an advertised speed which is again much slower than it actually can be. To my knowledge, a web server can be put under full load right away, and distributing computing projects use the most of your computer right off the bat. Why doesn't Tor run computational and/or bandwidth tests and advertise my relay at a much more actual speed? I don't see why a fast relay has to start at the very bottom of the barrel to begin with. I can see the logic in slowly ramping up connections in testing for stability and scalability, but the progress is slow because it's continually fighting against that existing average. I can set my requested average and burst bandwidth, but AFAIK I can't affect my advertised bandwidth. Why are things this way, and is there anything I can do to speed up the utilization growth?
Thanks in advance for any help you can provide, Jesse V.
On 09/11/2013 12:43 PM, Roger Dingledine wrote:> Many people set up new fast relays and then wonder why their bandwidth
is not fully loaded instantly. In this post I'll walk you through the lifecycle of a new fast non-exit relay, since Tor's bandwidth estimation and load balancing has gotten much more complicated in recent years.
https://blog.torproject.org/blog/lifecycle-of-a-new-relay
--Roger
I think the best thing to do is be patient. :)