[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Performance with potential mass use
- To: or-talk@xxxxxxxx
- Subject: Performance with potential mass use
- From: grarpamp <grarpamp@xxxxxxxxx>
- Date: Thu, 25 Feb 2010 23:38:05 -0500
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Thu, 25 Feb 2010 23:38:16 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Szr1reLZX6Vyxt0XxSMQBjMtqLY2tCIvlCBoIdl7mPo=; b=HpzD6rE8IK3Lb7/1UnIcK8igK0b8uX6RSQSdSfFJxHgBO/NaxivFGa6p48okmQoEkW Lp/LX9XPHBYcJxvbean+Fs8T4qSTUJyr46gdQvuq6Iv4jVg+tBCVXoFhAdcbRvQEkR7H mp+WJBnYnrLlrfC+cgdhH7qoDkhlO11gbddZ4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=OSntQaLnhfPte6Gax8sl+tY+kNxPIMZEiA22FuK9e62QO6RhplmNNujiAeqAJn182D DwYlonio0kcFqNLa76X5EVTqQZZx41UOlvH4BFD3J8+kc7nk8mUBvo8g6GaMAuW/xTl+ hpBr+BoTjirAMgYO0ooSjInijYkVOWlcLAGuA=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
Excluding bandwidth as that's probably the easiest
to guesstimate [6x each user's use for onion2onion case].
Assuming whatever typical usage patterns exist today,
and expecting a partial shift to include more bandwidth
intensive apps...
What sort of issues exist as each new set of say
1K/10K/100K/1000K users start using tor?
- Circuits tacked up funneling bits all the time?
- Circuit churn?
- Loads looking up directory info, HS descriptors?
- Blowing out cpu, ram, disk, OS limits to crunch it all?
- And anything else really, haven't much thought about it.
- How big is the impact of each affecting item?
- What fixes may be on paper or in the pipeline?
- Wikify this thread?
Kindof a general chat, no math proofs needed :)
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/