It is normal and you should wait. Eventually, your relay will get more weight, more connections, and a higher advertised bandwidth. You can somewhat see the effect when the one month graph is rendered on atlas. eg, see this new relay https://atlas.torproject.org/#details/C1B84214C9E336C82CEFF150A47C7FFDBC08C65B
Keep in mind, the network has ample middle relays at the moment so I would never expect the relay to use all the bandwidth that has been allocated. At least, that is my experience. https://metrics.torproject.org/bandwidth.html -Jeremy On Sat, Nov 1, 2014 at 10:16 AM, Rafael Rodriguez <[email protected]> wrote: > Maybe I should just wait longer but the 3 days unmetered has obviously been > passed already. That's why I'm asking about bwauths measurements. > > I was under the impression that after 3 days bwauths adjust your consensus > weight and raises your bandwidth estimate. In this case, the server is > simply capped at 20kb/s still while my "advertise bandwidth" is little over > 50kb/s. Since I have a 2MB/s relay, I'm expecting to see at least over > 100kb/s or 250kb/s measurements to make my relay a usable one. Yet the > advertised speed hasn't changed. Is that normal and should I just give it > more time? That's what I'm trying to understand. > > > > On 2014-11-01 07:00, Krbusek Christian wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > You may want to read the following, which should make this more clear. > > https://blog.torproject.org/blog/lifecycle-of-a-new-relayCheers > > Am 01.11.2014 um 10:46 schrieb Rafael Rodriguez: > > Anyone knows how often bwauths measures a relay? I don't understand why > directory authorities have not lifted the 20KB cap for my older relay. Now I > have doubts if it could be a problem with my server. This is a 2MB/s relay > with burst of 4MB/s to start tuning it and increase it later if stable, > which is not being used and has been running for over 3 days. Is it normal > for Relays to take longer than three days to start getting at least some > traffic and for directory authorities to lift the 20KB cap? Fingerprint > 48ADFCC561402D7EBB1CDE233F206B01D8FA0765 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBAgAGBQJUVL1GAAoJECgP5Pn8Zk3/cfoQAI9bMRyx8hl3B+V+vSLC7xoJ > sfQedgt15LRyJ/+Ru3tQaPDPOkleTKR3rCnKaDiRCmjxibWt4liRUBji2nzDPFJU > dcD0kEXqCA/H3jyIJWvKnkxvzUfAjCZ7Y7b16sGsJSgVfZ8UFin52loTDgjSz7zU > tgsqsOBIHT72gr/hbxRBzr3ZP8LZqTDA5baoLFAxnYyxIQwK5eRefI6zMP9cuiOA > FL4I60Tige+TBp8kDnyKdYosxRJFkkAJN3YCuHuewIgoV0pD/xkScEscYgqp+CWu > cMQkj5NDDMP/I5ZXw2a64Etq33Hc4SzEm4HvKquu05pS2QgClXu7pg8z2u1BCdPQ > 7uMZRyKfAnOOwITKVxsKXT5XJySFJXskMLgupLtp3iEA24GfLJTax0pa7xmOeEbb > nvt2kGdrKvAl3t4PgwvtwuFmfJoqXzjxWMJJRD2s3hXi0TS4WC1y1pccw+INXKsG > 7sV+dHhqDPwOHpFleHv4RG207Kx6P8+hbNjdeVI8iEelAhKoPfcUJDM/A4aa2ahd > GB+vZrnuInJlZJeg+hL28Xk1pOxwHtq046nhLosVY7YNDW6CHoD5aruWeQdCT1y5 > AFZ/xqOP+XPWMYj/UJLhWoBFTjYjSUZuxi5c4nGpKoK/OSc1GCZERx8Ec7mJrN2R > lzlnW4uBh7M+pvMrhRWl > =rF5K > -----END PGP SIGNATURE----- > _______________________________________________ > tor-relays mailing list > [email protected] > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > _______________________________________________ > tor-relays mailing list > [email protected] > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
