[tor-relays] potential relayor Address bug

[Tim Niemeyer]

Hi Nusenu

Am Samstag, den 24.03.2018, 15:18 +0000 schrieb nusenu:
> > At time of writing, the VM has 4 cores of Xeon E3-1230 V2 @ 3.30GHz
> 
> I estimate that you should be able to do ~90MByte/s per instance on
> that CPU
That would be much more than I expect. We will see.. I'm so curious. ;)

> > with 8 GB of main memory. 
> 
> this might be a bit tight if you run 8 instances since I expect an
> instance
> to use a bit more than 1GB of memory, but your limited exit policy
> might help you
> here. Just keep an eye on memory usage and drop an instance if you
> are swapping
> excessively.
I will keep an eye on it.

[..]
> 
> I filed a bug for this here:
> https://github.com/nusenu/ansible-relayor/issues/153
Thanks. I'm in the learning phase and wasn't sure about it. ;)

> Would you be able to send me your playbook and "ip address" output,
> so I can try to reproduce? (also off-list)
> (if you have more than a single default route/interface also the
> routing
> table)
I added the outputs to the issue.

Thanks
Tim

> thanks,
> nusenu
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20180324/905ccfcc/attachment-0001.sig>