Re: [tor-relays] First (positive) experiences with a Tor Relay on Raspberry Pi3
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
From: Yawning Angel <yawning@schwanenlied.me> To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] First (positive) experiences with a Tor Relay on Raspberry Pi3 Message-ID: <20160410182830.2be8c166@schwanenlied.me> Content-Type: text/plain; charset="utf-8"
On Sun, 10 Apr 2016 17:52:20 +0000 fr33d0m4all <fr33d0m4all@riseup.net> wrote:
I've just moved my Tor relay installation from my alix1.c embedded system (500Mhz CPU with 256Mb ram) which was able to offer only 4Mbps (100% CPU utilization) to a new Raspberry Pi3 (quad-core 1.2Ghz 64-bit cpu with 1 GB ram). Some days ago I've seen some messages on the ML about Pi2 performance (if I remember well) and I'd like to share my first experiences with Pi3. I have only 20Mbps connection in the uplink direction, so I'm offering about 15Mbps for Tor relay and I've just seen that it is able to offer 14Mbps with 40% of a single core utilization.. In conclusion, I think that a single relay on Pi3 can offer about 30-40 Mbps, and if you run 4 tor relays on the same Pi3 you can offer more than 100Mbps which is definitely not bad for such a small system. The only drawback is that you need to find a good way for keeping it cold, since after 1 hour of 1 core at 100% I've reached about 70?C with heatsinks on the CPU.
If you build tor against OpenSSL 1.1 on that target you will get a massive increase in performance due to support for the ARMv8 hardware AES acceleration.
This requires 0.2.8.x from the maint-028 branch (or master if you're brave) since I recently fixed tor (again) to compile with this version of the library, but the changes will be in the next 0.2.8 release candidate.
Regards,
Thank you very much Yawning for the news, I didn't know about that! I'm running stable 0.2.7.6 from the Jessie repo, I hope the new ARMv8-AES-enabled version will be out "soon" in the repo (but I don't think it will happen soon, at least for the stable branch, right?) BTW, I can't offer more than 14 Mbps, which are about 75% of my upload BW, so I can live for a while without AES acceleration :) You're work is really appreciated! Best regards, Fr33d0m4All _____________________________________________________________ PGP Key: 0DA8 7293 D561 3AEE A3C0 7F63 101F 316A F30E ECB4 IRC Nick: fr33d0m4all (OFTC & Freenode) _____________________________________________________________ -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXCsoWAAoJEBAfMWrzDuy05b8P/iHlAaKeVV4kOjujdENZs2Y1 xppzTRALgQcF+f2617j54zVO3gx9p/FkwEgt2ltqqJH8oSpaONBet6BBIrWL60/0 RUG0SYhtLJKAz722ou5XnP18a+ISt6Jq/peZuBxL5SBwjFg8SM1ibIpFpQlqrWNm 108KqF1TLEUEaRL99QO4lXNSDqTgdp0QzOZ3mkuXcorEgSDtcvtfMSwjUyVsGfVS t2JjYiZNGX36o1h0V3cFzN5pcELK/wkXVktxL0GRpJ3bTsoy5yfz+04QG9qFL6SL 4S/AAZ0GWObR+ZaRDY8Fo4X9PVTwN1qLhnXBhknUKeRl0K5u0ANOPvspxt5YpVaj K7Xb3tcVv958QyN6OIGNySUZh2TZ/7zzfgPj8rk4fWpwkZ2TxC0inLqUNTZrxY1W 9jbXTstp8HCWMYJ/aCO220+iyOFGXv0AeBsk5sr+onbkJxccIC4X8pYtm8DeocdZ +q+rIIJ+KcrJNtDLU/7LM4NhzEkTBfDQnFy3Vy5c68I0N39w3tjYyiNx/4JdoX+L vrLcTOZ09Mavfjbrcww27w1Aixlw0HU0aYlY8dHc5fJcHyc/en6Os9GDEGBpXCNh eptNWIlsNxuk9Pbeipb/1GxQt5X2GyAVoITqpBA7u0TO9vr0V+ZvlyY6Thx7qvpy jo2GqAnJQBfruuSD9ZTo =1lbW -----END PGP SIGNATURE-----
On Sun, 10 Apr 2016 21:48:06 +0000 fr33d0m4all <fr33d0m4all@riseup.net> wrote: [snip]
Thank you very much Yawning for the news, I didn't know about that! I'm running stable 0.2.7.6 from the Jessie repo, I hope the new ARMv8-AES-enabled version will be out "soon" in the repo (but I don't think it will happen soon, at least for the stable branch, right?)
0.2.8.x will be in a stable repo shortly. However as far as I know, we do not separately build OpenSSL packages (and the 1.1.0 series is still in pre-release state), so you will either need to be patient, or wait the 15 years it takes for Debian to update anything[0].
BTW, I can't offer more than 14 Mbps, which are about 75% of my upload BW, so I can live for a while without AES acceleration :)
Well, crypto being more efficient would reduce load on the box and lessen the likelyhood of it catching fire. :P Realistically I'd wait till there at least is a formal OpenSSL 1.1.0 release before using it for more than testing. But I figured it would be good to note that the RasPi3 will benefit. Regards, -- Yawning Angel [0]: Obvious hyperbole is obvious.
I have also had heat issues with raspb. Solution in my setup was a small dollar store fan for air movement. My plan today is to put up another relay on another pi. ps. I must say that the tor community is one of the most helpful and supportive groups ive come across. Not because of our core purpose. It is because we already are in a position to help the world and we top that with a email list that is always full of people willing to help their fellow man/woman help the world more efficiently. These selfless acts do not go unnoticed. Id sit in a relay center helping you all back 9-5 if time allowed Together we are awesome. Thats my speech for the year. Thank you all! On Apr 10, 2016 6:30 PM, "Yawning Angel" <yawning@schwanenlied.me> wrote:
On Sun, 10 Apr 2016 21:48:06 +0000 fr33d0m4all <fr33d0m4all@riseup.net> wrote:
[snip]
Thank you very much Yawning for the news, I didn't know about that! I'm running stable 0.2.7.6 from the Jessie repo, I hope the new ARMv8-AES-enabled version will be out "soon" in the repo (but I don't think it will happen soon, at least for the stable branch, right?)
0.2.8.x will be in a stable repo shortly. However as far as I know, we do not separately build OpenSSL packages (and the 1.1.0 series is still in pre-release state), so you will either need to be patient, or wait the 15 years it takes for Debian to update anything[0].
BTW, I can't offer more than 14 Mbps, which are about 75% of my upload BW, so I can live for a while without AES acceleration :)
Well, crypto being more efficient would reduce load on the box and lessen the likelyhood of it catching fire. :P
Realistically I'd wait till there at least is a formal OpenSSL 1.1.0 release before using it for more than testing. But I figured it would be good to note that the RasPi3 will benefit.
Regards,
-- Yawning Angel
[0]: Obvious hyperbole is obvious.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hey, To see current temperature of my RPi v1 + v2, I'm using "phpsysinfo" http://phpsysinfo.sourceforge.net/ You need a webserver + php, it's php scripts that can give you informations on a webpage about temp, quotas, hdd... It's not monitoring 24/24, only when you refresh/surf the webpage. To see the RPi temp with this tool, in phpsysinfo.ini : SENSOR_PROGRAM="PiTemp" (and enable javascript in your browser to see "/index.php?disp=dynamic" version) Munin was too heavy on the RPi v1... not tested on the v2...And I don't remember if it was able to catch and draw temperature... I've read on some websites RPi v3 can be really hot when it's working... :( And thx for your positive message, it's always nice to read this ! Le 11/04/2016 16:00, Odd Sec a écrit :
I have also had heat issues with raspb. Solution in my setup was a small dollar store fan for air movement. My plan today is to put up another relay on another pi.
ps. I must say that the tor community is one of the most helpful and supportive groups ive come across. Not because of our core purpose. It is because we already are in a position to help the world and we top that with a email list that is always full of people willing to help their fellow man/woman help the world more efficiently. These selfless acts do not go unnoticed. Id sit in a relay center helping you all back 9-5 if time allowed
Together we are awesome. Thats my speech for the year.
Thank you all!
On Apr 10, 2016 6:30 PM, "Yawning Angel" <yawning@schwanenlied.me <mailto:yawning@schwanenlied.me>> wrote:
On Sun, 10 Apr 2016 21:48:06 +0000 fr33d0m4all <fr33d0m4all@riseup.net <mailto:fr33d0m4all@riseup.net>> wrote:
[snip]
> Thank you very much Yawning for the news, I didn't know about that! > I'm running stable 0.2.7.6 from the Jessie repo, I hope the new > ARMv8-AES-enabled version will be out "soon" in the repo (but I don't > think it will happen soon, at least for the stable branch, right?)
0.2.8.x will be in a stable repo shortly. However as far as I know, we do not separately build OpenSSL packages (and the 1.1.0 series is still in pre-release state), so you will either need to be patient, or wait the 15 years it takes for Debian to update anything[0].
> BTW, I can't offer more than 14 Mbps, which are about 75% of my upload > BW, so I can live for a while without AES acceleration :)
Well, crypto being more efficient would reduce load on the box and lessen the likelyhood of it catching fire. :P
Realistically I'd wait till there at least is a formal OpenSSL 1.1.0 release before using it for more than testing. But I figured it would be good to note that the RasPi3 will benefit.
Regards,
-- Yawning Angel
[0]: Obvious hyperbole is obvious.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
participants (4)
-
fr33d0m4all -
Odd Sec -
Pierre L. -
Yawning Angel