Opened 8 years ago

Closed 7 years ago

#5629 closed enhancement (implemented)

How many EC2 bridges do we have?

Reported by: runa Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/Website Version:
Severity: Keywords:
Cc: arma, kaner Actual Points: 2
Parent ID: Points:
Reviewer: Sponsor:

Description

We are encouraging people to set up bridges in the Amazon cloud, so it would be nice if we could also count the number of EC2 bridges we have.

Last time aagbsn counted EC2 bridges, the number was ~256. The time before it was ~300, and before that it was ~600. When Roger counted, it was ~90. Either something's up with BridgeDB, our Tor Cloud images, or someone's counting bridges wrong. Which one is it?

Child Tickets

Attachments (1)

ec2bridges-2012-05-31.png (35.3 KB) - added by karsten 7 years ago.
Number of EC2 bridges

Download all attachments as: .zip

Change History (11)

comment:1 Changed 8 years ago by aagbsn

This is the script I run to get the number of ec2 bridges:

grep "^router ec2bridge" /srv/bridges.torproject.org/from-authority/bridge-descriptors  | awk '{print $3}' | uniq | wc -l

Field $3 is the IP address. Field $2 is the nickname. So far I have observed that the count is the same whether I count by unique IP address or nickname.

Did I miss something?

comment:2 Changed 8 years ago by karsten

The bridge-descriptors file contains all the server descriptors that Tonga knows about. You'll probably want to look at the "r " lines of networkstatus-bridges, more specifically only at those with " Running" in the subsequent "s " line.

By the way, I don't think we should derive any statistical information from data which is too sensitive to be published. In this case it might mean that we should stop scrubbing nicknames in sanitized bridge descriptors. That would allow us to have the number Runa wants to know for the last few months, not just single days. But if we think the nickname is too sensitive, then we shouldn't derive this statistic at all.

comment:3 Changed 8 years ago by arma

$ grep "^r ec2bridge" networkstatus-bridges -A1|grep " Running"|wc -l
158

comment:4 Changed 8 years ago by runa

Do we know how many were created after March 15 this year?

comment:5 in reply to:  4 ; Changed 7 years ago by aagbsn

I agree with Karsten -- we shouldn't report statistics that cannot be verified -- after all, someone might mess up and report the wrong numbers... :\

That said, knowing the # of ec2bridges is useful internally.

Replying to runa:

Do we know how many were created after March 15 this year?

If an unsanitized archive of the bridge descriptors exist we can find out. Ponticum.tpo does not keep an archive of the bridge descriptors.

Also:

grep "^r ec2bridge" /srv/bridges.torproject.org/from-authority/networkstatus-bridges -A1|grep " Running"|wc -l
38

Do we have an idea why the number of bridges seems to fluctuate so much?

comment:6 in reply to:  5 Changed 7 years ago by karsten

Replying to aagbsn:

Replying to runa:

Do we know how many were created after March 15 this year?

If an unsanitized archive of the bridge descriptors exist we can find out. Ponticum.tpo does not keep an archive of the bridge descriptors.

We could find out, but we shouldn't. I just created #5684 to discuss keeping bridge nicknames in sanitized descriptors. Once we have nicknames in sanitized descriptors we can run that analysis. And I'm happy to sanitize all bridge descriptors once again. But if there are good reasons not to keep nicknames, we won't find out.

Changed 7 years ago by karsten

Attachment: ec2bridges-2012-05-31.png added

Number of EC2 bridges

comment:7 Changed 7 years ago by karsten

See the attached graph for a count of EC2 bridges based on their nicknames.

comment:8 Changed 7 years ago by karsten

Component: BridgeDBMetrics Website
Type: taskenhancement

Runa asked me to make this graph a part of https://metrics.torproject.org/network.html. Making this a Metrics Website ticket.

comment:9 Changed 7 years ago by karsten

Owner: changed from aagbsn to karsten
Status: newassigned

comment:10 Changed 7 years ago by karsten

Actual Points: 2
Resolution: implemented
Status: assignedclosed
Note: See TracTickets for help on using tickets.