Hello!
I'd like to collect some samples for how many MBit/s on a single tor daemon are possible on given CPU model before it is limited by the CPU.
If your single tor daemon routes more than 350 MBit/s in each direction and you are running on bare metal it would be awesome if you could share your - CPU model (ideally a link to ark.intel.com if it is an intel cpu) - avg. daily CPU usage (ie. from munin graphs) - actual traffic (MBit/s) - optional: relay fingerprint
thank you! tor7
tor7:
Hello!
I'd like to collect some samples for how many MBit/s on a single tor daemon are possible on given CPU model before it is limited by the CPU.
If your single tor daemon routes more than 350 MBit/s in each direction and you are running on bare metal it would be awesome if you could share your
- CPU model (ideally a link to ark.intel.com if it is an intel cpu)
- avg. daily CPU usage (ie. from munin graphs)
- actual traffic (MBit/s)
- optional: relay fingerprint
+OS would be wonderful.
g
On 4 Feb 2018, at 07:55, George george@queair.net wrote:
tor7:
Hello!
I'd like to collect some samples for how many MBit/s on a single tor daemon are possible on given CPU model before it is limited by the CPU.
If your single tor daemon routes more than 350 MBit/s in each direction and you are running on bare metal it would be awesome if you could share your
- CPU model (ideally a link to ark.intel.com if it is an intel cpu)
- avg. daily CPU usage (ie. from munin graphs)
- actual traffic (MBit/s)
- optional: relay fingerprint
+OS would be wonderful.
You can test how much Tor traffic your machine can handle with chutney:
git clone https://git.torproject.org/chutney.git # Pass 100 MB of random data through a 3-hop tor path on your local machine chutney/tools/test-network.sh --data-bytes 104857600
Chutney runs a Tor client, 3 relays, and a python script, so your results will be slightly lower than the maximum. But they are much more reproducible, because they don't depend on your network connection.
T
You can test how much Tor traffic your machine can handle with chutney:
I'm asking to find out which CPU to buy (I don't have the hardware yet to test and would like to find out before buying), that is why I was asking others for their eperience.
git clone https://git.torproject.org/chutney.git # Pass 100 MB of random data through a 3-hop tor path on your local machine
chutney/tools/test-network.sh --data-bytes 104857600
I was curious, is this expected output?
chutney/tools/test-network.sh --data-bytes 104857600 test-network.sh: using CHUTNEY_DNS_CONF '/dev/null' test-network.sh: no $TOR_DIR, chutney will use $PATH for tor binaries test-network.sh: $CHUTNEY_PATH not valid, using this script's location Using Python 2.7.14 Sending SIGINT to nodes Waiting for nodes to finish. Removing stale lock file for test000a ... Removing stale lock file for test001a ... Removing stale lock file for test002a ... Removing stale lock file for test003ba ... Removing stale lock file for test004r ... Removing stale lock file for test005r ... Removing stale lock file for test006r ... Removing stale lock file for test007r ... Removing stale lock file for test008br ... Removing stale lock file for test009c ... Removing stale lock file for test010bc ... Removing stale lock file for test011h ... bootstrap-network.sh: bootstrapping network: bridges+hs Using Python 2.7.14 NOTE: creating '/home/user/chutney/tools/../net/nodes.1517745089', linking to '/home/user/chutney/tools/../net/nodes' Creating identity key /home/user/chutney/net/nodes/000a/keys/authority_identity_key for test000a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/user/chutney/net/nodes/000a/keys/authority_identity_key -s /home/user/chutney/net/nodes/000a/keys/authority_signing_key -c /home/user/chutney/net/nodes/000a/keys/authority_certificate -m 12 -a 127.0.0.1:7000 Creating identity key /home/user/chutney/net/nodes/001a/keys/authority_identity_key for test001a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/user/chutney/net/nodes/001a/keys/authority_identity_key -s /home/user/chutney/net/nodes/001a/keys/authority_signing_key -c /home/user/chutney/net/nodes/001a/keys/authority_certificate -m 12 -a 127.0.0.1:7001 Creating identity key /home/user/chutney/net/nodes/002a/keys/authority_identity_key for test002a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/user/chutney/net/nodes/002a/keys/authority_identity_key -s /home/user/chutney/net/nodes/002a/keys/authority_signing_key -c /home/user/chutney/net/nodes/002a/keys/authority_certificate -m 12 -a 127.0.0.1:7002 Creating identity key /home/user/chutney/net/nodes/003ba/keys/authority_identity_key for test003ba with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/user/chutney/net/nodes/003ba/keys/authority_identity_key -s /home/user/chutney/net/nodes/003ba/keys/authority_signing_key -c /home/user/chutney/net/nodes/003ba/keys/authority_certificate -m 12 -a 127.0.0.1:7003 Using Python 2.7.14 Starting nodes
Using Python 2.7.14 test000a is running with PID 963 test001a is running with PID 966 test002a is running with PID 969 test003ba is running with PID 972 test004r is running with PID 975 test005r is running with PID 978 test006r is running with PID 981 test007r is running with PID 984 test008br is running with PID 987 test010bc is running with PID 993 test011h is running with PID 996 11/12 nodes are running
-> returns to cli prompt.
You asked:
Is this the expected output?
On 4 Feb 2018, at 22:59, tor7 tor7@mailbox.org wrote:
test000a is running with PID 963 test001a is running with PID 966 test002a is running with PID 969 test003ba is running with PID 972 test004r is running with PID 975 test005r is running with PID 978 test006r is running with PID 981 test007r is running with PID 984 test008br is running with PID 987 test010bc is running with PID 993 test011h is running with PID 996 11/12 nodes are running
No, it looks like "test009" failed to launch. Maybe one of its ports conflicts with an existing service on your machine?
I also forgot that we changed the default network to a big network. If you pass "--flavour basic-min" to the script, you'll get a minimal network. And the results will be much more reliable.
I think it only has 5 tor instances, so it should launch ok, too.
T
tor-relays@lists.torproject.org
-
George -
teor -
tor7