Delivery-Date: Tue, 16 Dec 2014 11:08:14 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00,PLING_QUERY,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id B4BBD1E0B01;
	Tue, 16 Dec 2014 11:08:12 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4BB6531EA4;
	Tue, 16 Dec 2014 16:08:08 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9073531E66
 for <tor-talk@lists.torproject.org>; Tue, 16 Dec 2014 16:08:05 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id y_2RE0rRut6s for <tor-talk@lists.torproject.org>;
 Tue, 16 Dec 2014 16:08:05 +0000 (UTC)
Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 57E36315B9
 for <tor-talk@lists.torproject.org>; Tue, 16 Dec 2014 16:08:05 +0000 (UTC)
Mime-Version: 1.0
Date: Tue, 16 Dec 2014 16:07:56 +0000
From: fuckyouhosting@ruggedinbox.com
To: tor-talk@lists.torproject.org
Message-ID: <c9d7261dfa1e0986f9c71eb845585956@ruggedinbox.com>
X-Sender: fuckyouhosting@ruggedinbox.com
Subject: [tor-talk] =?utf-8?q?=28D=29DOS_over_Tor_network_=3F_Help_!_=5BSo?=
 =?utf-8?q?lved_=3F=5D?=
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Hi all, little follow up.
We ( fuckyouhotwkd3xh.onion ) rewrote the hosting engine and now it 
splits the virtual hosts over multiple Tor session, 30 hidden services 
per Tor session.
We are currently hosting 636 vhost, php-fpm consumes 671MB of RAM
and 21 Tor session, consuming 458MB of RAM.
On a 2GB of RAM server, all looks ok, all the hidden services seems up
and the infamous "Your Guard XXX is failing more circuits than usual" 
error shows up very rarely.

In short, we advise HS hosters not to overload a single Tor session with 
too many HSs.

Thank you.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

