Hello @all, I've currently 10 processes which requests the hidden service via the same TOR daemon. The TOR daemon receives every hour a HUP signal. As fas as I understand my current setup doesn't help very much because the circuits are always reused and only built new every hour after the HUP signal. Am I correct? ~Josef Am 08.07.2015 um 16:07 schrieb Thomas White: > Just to expand on s7r's number, I just pulled the latest logs from the > servers and compiled a quick breakdown of the HTTP codes, bandwidth > etc for anyone interested: > > HTTP Code: 200 (OK) > Bandwidth used (bytes): 690,400,220,422 > Hits: 4,784,288 > > > HTTP Code: 206 (Partial Content) > Bandwidth used (bytes): 5,202,918 > Hits: 64 > > > HTTP Code: 304 (Not Modified) > Bandwidth used (bytes): 52,059 > Hits: 259 > > > HTTP Code: 404 (Not Found) > Bandwidth used (bytes): 266,053 > Hits: 611 > > > HTTP Code: 403 (Forbidden) > Bandwidth used (bytes): 2,908 > Hits: 7 > > > HTTP Code: 408 (Request Timeout) > Bandwidth used (bytes): 0 > Hits: 5,442 > > > Total bandwidth usage (bytes): 690,405,744,360 (690 GB) > > Total hits: 4,790,671 > > > Not bad for a few days work guys! > > T > > > > > On 08/07/2015 03:00, s7r wrote: > > *Numbers look good: Over 4 million hits in 7 days.* > > > I want again to use this opportunity to say THANK YOU to everyone > > who is contributing and stress testing. 4 million requests tell me > > people are putting quite some effort into it. Please continue to > > stress test as much as you can in the next days. After I collect > > some rendezvous circuit stats also, we will stop the test - don't > > want to overkill the network, prefer to leave more bandwidth > > capacity for users. > > > I was waiting to have some rendezvous circuit statistics as well, > > to compare them with the hits on the webserver and have an overview > > on the circuits stats and average number of requests per circuit. > > Hopefully this will happen in the next days. Since you asked, here > > are the exact numbers now. > > > The service was started 1st July 2015. Here are the counts today, > > 8th July (little over 7 days of uptime): > > > Failback instance #1: 956281 Failback instance #2: 732187 Failback > > instance #3: 837818 Failback instance #4: 768636 Failback instance > > #5: 911546 ============================= TOTAL: 4206468 > > > There are no significant warnings or errors - the same instances > > are running since service first started, no reboot or application > > restart. I am happy with how it works. As you can see we have *over > > 4 million hits*. The number of requests per failback instance > > confirms the load is fairly spread. > > > Hidden service http://eujuuws2nacz4xw4.onion/ up and strong! > > > On 7/8/2015 1:48 AM, tqr2813d376cjozqap1l@xxxxxxxxxxxx wrote: > >> 4. Jul 2015 22:57 by s7r@xxxxxxxxxx <mailto:s7r@xxxxxxxxxx>: > > >> After little over 3 days of uptime, the OnionBalance hidden > >> service http://eujuuws2nacz4xw4.onion > >> <http://eujuuws2nacz4xw4.onion/> was successfully accessed over 1 > >> Million times. There was no complaint in any of the running Tor > >> instance s. > > > > >> Hey s7r, things still looking OK? How are the numbers now? > >
Attachment:
signature.asc
Description: OpenPGP digital signature
-- tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk