If you don't mind my asking, why specifically in Europe? Doesn't the CPU also come into play? Thanks. Lavender - Tor Relay Operator Le mercredi 22 juillet 2026 à 16:25, Tor at 1AEO via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx> a écrit : > If you're in Europe, it's possible with one relay. > If you're outside Europe, it'll usually take more than one relay. > > Give the relay at least a few weeks to get consensus weight allocated. > > > Sent from Proton Mail for Android. > > -------- Original Message -------- > On Wednesday, 07/22/26 at 03:42 Marco Moock via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx> wrote: > Am 21.07.26 um 14:02 schrieb Lavender I Tor Relay via tor-relays: > > I was wondering if it's possible to allocate 1 Gbps of bandwidth to > > my Tor relay, or if it would be better to create multiple instances > > on the same server? > > > > I have a dedicated server in a data center. When I look at the list > > of the fastest relays, I see that some manage to reach 1 Gbps on a > > single instance, but I assume that requires a very powerful CPU and > > a very high single-core clock speed, given that my CPU is a bit old. > > Simply try it. > The worst thing that can happen is that the throughput will be lower. > You can then check the CPU usage. > > > -- > Gruß > Marco > Muell und Spam bitte an abfalleimer2002@xxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ > tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx > _______________________________________________ > tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx >
Attachment:
publickey - lavender-tor@proton.me - 0xE49C935B.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx