-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I assumed that 2 Tor at the same ip address would get haöf of the consensus of the previously runnning only one Tor relay at the same hardware. But it semes, that both Tor relays get now the same value as the one before.
Is this intended ?
- -- Toralf PGP C4EACDDE 0076E94E
On 29 Oct 2017, at 22:18, Toralf Förster toralf.foerster@gmx.de wrote:
I assumed that 2 Tor at the same ip address would get haöf of the consensus of the previously runnning only one Tor relay at the same hardware. But it semes, that both Tor relays get now the same value as the one before.
Is this intended ?
Possibly.
Are the relays CPU-limited, or bandwidth-limited?
T
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 10/29/2017 01:24 PM, teor wrote:
Possibly.
Are the relays CPU-limited, or bandwidth-limited?
Not at all, neither limited by a config value nor by the hardware (1GBit/s, 200 MBit/s guaranteed, i7-3930, all non-Tor processes have "nice" in front, ids are 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA and 6EABEBF38CE7E3DF672C4DB01383606FE3EB2215)
- -- Toralf PGP C4EACDDE 0076E94E
On 29 Oct 2017, at 23:30, Toralf Förster toralf.foerster@gmx.de wrote:
On 10/29/2017 01:24 PM, teor wrote: Possibly.
Are the relays CPU-limited, or bandwidth-limited?
Not at all, neither limited by a config value nor by the hardware (1GBit/s, 200 MBit/s guaranteed, i7-3930, all non-Tor processes have "nice" in front, ids are 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA and 6EABEBF38CE7E3DF672C4DB01383606FE3EB2215)
I'm sorry, this doesn't help me answer your question.
Usually, a relay is limited by either the available network bandwidth, or by the speed of a single CPU core on the machine.
If the first relay used all the available bandwidth, then two relays will eventually have lower consensus weight values.
If the first relay used all of a single CPU core for its main thread, then the two relays will eventually have similar consensus weight values.
T
tor-relays@lists.torproject.org