If I set up OnionBalance, and have two backend onion servers - how would I know if I need to add another onion server and balance it further? I can easily monitor the CPU/Memory usage of the onion servers, but does that tell the whole story? I assume there's potentially other ways connection failures can occur... -tom
On 3 Feb 2017, at 05:27, Tom Ritter <tom@ritter.vg> wrote:
If I set up OnionBalance, and have two backend onion servers - how would I know if I need to add another onion server and balance it further?
I can easily monitor the CPU/Memory usage of the onion servers, but does that tell the whole story? I assume there's potentially other ways connection failures can occur...
-tom
Standard website uptime and performance monitoring on the top-level .onion address and each of the backends would display most user-visible issues. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
Youjust use A reverse proxy, like squid is what alot of ppl use or nginx then regular monitoring should work, useing email notice is nice Tom Ritter <tom@ritter.vg> skrev: (2 februari 2017 19:27:31 CET)
If I set up OnionBalance, and have two backend onion servers - how would I know if I need to add another onion server and balance it further?
I can easily monitor the CPU/Memory usage of the onion servers, but does that tell the whole story? I assume there's potentially other ways connection failures can occur...
-tom _______________________________________________ tor-onions mailing list tor-onions@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions
-- Sincerly flipchan - LayerProx dev
I concur with the discussion so far; once you are into the multi-tor-daemon deployments the "tuning" becomes rather organic. I would look at network throughput on the tor nodes which are serving as reverse-proxies, and correlate that against load. Frankly: Facebook currently delivers its entire onion service through 2 daemons per each of 3 onion addresses (www, cdn, sbx) for six daemons total; the chokepoint is far more likely to be the content-delivery backend. -a
participants (4)
-
Alec Muffett -
Flipchan -
teor -
Tom Ritter