[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-dev] Summary of meek's costs, May 2015



Here's the summary of meek's CDN fees for May 2015.

            App Engine +   Amazon + Azure = total by month
February 2014    $0.09 +       -- +    -- =    $0.09
March 2014       $0.00 +       -- +    -- =    $0.00
April 2014       $0.73 +       -- +    -- =    $0.73
May 2014         $0.69 +       -- +    -- =    $0.69
June 2014        $0.65 +       -- +    -- =    $0.65
July 2014        $0.56 +    $0.00 +    -- =    $0.56
August 2014      $1.56 +    $3.10 +    -- =    $4.66
September 2014   $4.02 +    $4.59 + $0.00 =    $8.61
October 2014    $40.85 +  $130.29 + $0.00 =  $171.14
November 2014  $224.67 +  $362.60 + $0.00 =  $587.27
December 2014  $326.81 +  $417.31 + $0.00 =  $744.12
January 2015   $464.37 +  $669.02 + $0.00 = $1133.39
February 2015  $650.53 +  $604.83 + $0.00 = $1255.36
March 2015     $690.29 +  $815.68 + $0.00 = $1505.97
April 2015     $886.43 +  $785.37 + $0.00 = $1671.80
May 2015       $871.64 +  $896.39 + $0.00 = $1768.03
--
total by CDN  $4163.89 + $4689.18 + $0.00 = $8853.07 grand total

The number of users stayed in the range of 3000 to 4000. There are a few
days of missing data. I think the big increase to 6000+ users on the day
before the gap is a bad measurement.

https://metrics.torproject.org/userstats-bridge-transport.html?graph=userstats-bridge-transport&start=2015-03-01&end=2015-05-31&transport=meek

On May 22 I asked the operator of the meek-google bridge to rate-limit
the bridge to 1.5 MB/s in an attempt to limit costs. Since then we
further limited it to 1.1 MB/s. It pains me to do that, but I need to
find a way to make the operation of this transport sustainable. I
estimated the rates to keep us under the $500/month credit we have from
Google.

I may also rate-limit meek-amazon too. If you want to set up your own
bridge and CDN instance without rate limiting, I can help you do that if
you email me. Here are some docs to look at:
https://trac.torproject.org/projects/tor/wiki/doc/meek#Howtorunameek-serverbridge
https://trac.torproject.org/projects/tor/wiki/doc/meek#GoogleAppEngine
https://trac.torproject.org/projects/tor/wiki/doc/meek#AmazonCloudFront
https://trac.torproject.org/projects/tor/wiki/doc/meek#MicrosoftAzure


== App Engine a.k.a. meek-google ==

Total bandwidth was down, probably because of the new rate limiting.
Oddly, instance hours were way up, perhaps for the same reason. The rate
limiting happens at the bridge, so it's possible that it's wasting
resources at the App Engine level.

Here is how the Google costs broke down:
	5359 GB             $643.07
	4571 instance hours $228.57
Compared to the previous month:
	6304 GB             $756.59
	2597 instance hours $129.84

In the graph you can really see the impact of limiting bandwidth.
Interestingly, the number of users did not decrease. It's just going
slower for them :(

https://globe.torproject.org/#/bridge/88F745840F47CE0C6A4FE61D827950B06F9E4534


== Amazon a.k.a. meek-amazon ==

Requests were up about 13% and bandwidth was up about 15%.

Asia Pacific (Singapore)     132M requests $158.86   973 GB $129.18
Asia Pacific (Sydney)        633K requests   $0.79     4 GB   $0.58
Asia Pacific (Tokyo)          47M requests  $57.04   331 GB  $43.14
EU (Ireland)                 184M requests $221.61  1847 GB $147.56
South America (Sao Paulo)      7M requests  $17.04    49 GB  $11.73
US East (Northern Virginia)   68M requests  $68.57   509 GB  $40.27
--
total                        441M requests $523.91  3715 GB $372.46

https://globe.torproject.org/#/bridge/3FD131B74D9A96190B1EE5D31E91757FADA1A4F3


== Azure a.k.a. meek-azure ==

meek-azure increased about 30% again this month. You should only count
on it working for another 3 months.

https://onionoo.torproject.org/bandwidth?fingerprint=AA033EEB61601B2B7312D89B62AAA23DC3ED8A34
Estimated bandwidth use this month:
	2015-05 2592 GB
Compared to last month:
	2015-04 1982 GB

https://globe.torproject.org/#/bridge/AA033EEB61601B2B7312D89B62AAA23DC3ED8A34


David Fifield


Earlier reports in this series:
https://lists.torproject.org/pipermail/tor-dev/2014-August/007429.html
https://lists.torproject.org/pipermail/tor-dev/2014-October/007576.html
https://lists.torproject.org/pipermail/tor-dev/2014-November/007716.html
https://lists.torproject.org/pipermail/tor-dev/2014-December/007916.html
https://lists.torproject.org/pipermail/tor-dev/2015-January/008082.html
https://lists.torproject.org/pipermail/tor-dev/2015-February/008235.html
https://lists.torproject.org/pipermail/tor-dev/2015-March/008427.html
https://lists.torproject.org/pipermail/tor-dev/2015-April/008596.html
https://lists.torproject.org/pipermail/tor-dev/2015-May/008767.html

PNG image

PNG image

PNG image

PNG image

_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev