[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Regarding directory updates
- To: or-talk@xxxxxxxxxxxxx
- Subject: Regarding directory updates
- From: Arrakis Tor <arrakistor@xxxxxxxxx>
- Date: Sat, 1 Oct 2005 11:05:13 -0500
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Sat, 01 Oct 2005 12:05:28 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=pS76dizr6oQjDI6nDhgilZrHz/6vgZncHgBWfujMhNn4x2jAqYMWe2VvxOH68XK9Agb+F7JeTxb6zEiiTkcM/Wo+i8vpZUd6mU0ULKlVISQ3iO/k3TolFCwGtqqPm6XghNHdMTg/2QODZJSayoizq1B7vldS2mU+4azXyN6xIIs=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
I was thinking that if Torpark becomes popular, there are many people
outside of China who would use it. This creates the possibility of
clogging tor with thousands of extra circuits while not giving back
any bandwidth. So I am going to build a server configuration for it.
However, most people probably won't stay connected for longer than 30
minutes to 2 hours at a time. I notice when I start Tor, I don't start
getting lots of circuits very fast. Tor is not using my bandwidth
efficiently from the beginning, it has to ramp up to consume all the
available bandwidth. I am wondering if it would be better to use the
Dirport as a push technology so servers can get updated really fast.
Is there a better solution for optimizing that 30 minute to 2 hour
time slot of the potential Torpark servers?
ST