[tor-relays] How to reduce tor CPU load on a single bridge?

[Gary C. New]

David,
I see that the metrics change has been reverted.
If/When the metrics change is implemented, will loadbalanced Tor Relay Nodes need to be uniquely named or will they all be able to use the same nickname?
I'm glad to hear your loadbalanced Snowflake Relay continues to work well.
Thanks, again, for your efforts.
Respectfully,

Gary—
This Message Originated by the Sun.
iBigBlue 63W Solar Array (~12 Hour Charge)
+ 2 x Charmast 26800mAh Power Banks
= iPhone XS Max 512GB (~2 Weeks Charged) 

    On Thursday, March 3, 2022, 6:59:26 PM MST, David Fifield <david at bamsoftware.com> wrote:  
 
 On Thu, Mar 03, 2022 at 08:13:34PM +0000, Gary C. New wrote:
> Has Tor Metrics implemented your RFC related to Written Bytes per Second and
> Read Bytes per Second on Onionoo?
> 
> As of the 27th of February, I've noticed a change in reporting that accurately
> reflects the aggregate of my Tor Relay Nodes opposed to the previously reported
> Single Tor Node. Are you seeing a similar change for snowflake.torproject.org?

You're right. I see a change since 2022-02-27, but in the case of the
snowflake bridge the numbers look wrong, about 8× too high. I posted an
update on the issue. Thanks for noticing.

https://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/issues/40022#note_2783524

> Additionally, other than the hourly stacktrace errors in the syslog, the
> secure_onion_key workaround seems to be working well without any ill
> side-effects. I've been able to operate with the same secure_onion_key for
> close to 5 weeks, now. Have you run into any issues?

Yes, it's still working well here.
_______________________________________________
tor-relays mailing list
tor-relays at lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20220304/0e6f4a7e/attachment-0001.htm>