Here's the summary of meek's CDN fees for December 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 June 2015 $601.83 + $820.00 + $0.00 = $1421.83 July 2015 $732.01 + $837.08 + $0.00 = $1569.09 August 2015 $656.76 + $819.59 + $154.89 = $1631.24 September 2015 $617.08 + $710.75 + $490.58 = $1818.41 October 2015 $672.01 + $110.72 + $300.64 = $1083.37 November 2015 $602.35 + $474.13 + $174.18 = $1250.66 December 2015 $561.29 + $603.27 + $172.60 = $1337.16 -- total by CDN $8607.22 + $9064.72 + $1292.89 = $18964.83 grand total
https://metrics.torproject.org/userstats-bridge-transport.html?graph=usersta...
The number of users increased by about 1,000 in December 2015.
meek-google had an outage as a result of a server migration between 23 November and 4 December.
I set up a bridge that is not rate-limited. If you use it, your meek will go a lot faster. https://bugs.torproject.org/17890 The catch is that you have to set up a CDN or upload a PHP file yourself. Here are some docs to look at: https://trac.torproject.org/projects/tor/wiki/doc/meek#Howtorunameek-serverb... 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 ==
Here is how the Google costs broke down: 2528 GB $303.39 5158 instance hours $257.90 Compared to the previous month: 2162 GB $259.52 6856 instance hours $342.83
https://globe.torproject.org/#/bridge/88F745840F47CE0C6A4FE61D827950B06F9E45...
== Amazon a.k.a. meek-amazon ==
Asia Pacific (Singapore) 56M requests $67.98 425 GB $58.83 Asia Pacific (Sydney) 2M requests $3.37 10 GB $1.41 Asia Pacific (Tokyo) 30M requests $37.14 242 GB $31.64 EU (Ireland) 142M requests $171.48 968 GB $76.50 South America (Sao Paulo) 5M requests $11.03 31 GB $7.46 US East (Northern Virginia) 86M requests $86.54 635 GB $49.88 -- total 324M requests $377.54 2314 GB $225.72
https://globe.torproject.org/#/bridge/F4AD82B2032EDEF6C02C5A529C42CFAFE51656...
== Azure a.k.a. meek-azure ==
Zone 1 1560 GB $135.71 Zone 2 267 GB $ 36.89 -- total 1827 GB $172.60
https://globe.torproject.org/#/bridge/AA033EEB61601B2B7312D89B62AAA23DC3ED8A...
Earlier reports in this series: https://trac.torproject.org/projects/tor/wiki/doc/meek#Costs
On 01/11/2016 12:47 PM, David Fifield wrote:
December 2015 $561.29 + $603.27 + $172.60 = $1337.16 ... The number of users increased by about 1,000 in December 2015.
Thanks for the report, David.
There are now ~1800 users on meek-google sharing 8 Mbits. Of course, it's also possible that many are lurking. I wonder if we should think of a way to load-balance the CDNs a bit more, assuming Azure is accessible from China. Perhaps we could re-order or at least clarify the bridge options in the Tor Browser. Since it's logistically challenging to get bridges from inside a censored country, it's possible that users try the various bridge options using the built-in bridges (which are likely blocked) before discovering that meek works, so they use that. I wonder how we could encourage users to use other transports that are likely faster, then use meek as a last resort.
On Mon, Jan 11, 2016 at 01:19:22PM -0900, Jesse V wrote:
On 01/11/2016 12:47 PM, David Fifield wrote:
December 2015 $561.29 + $603.27 + $172.60 = $1337.16 ... The number of users increased by about 1,000 in December 2015.
Thanks for the report, David.
There are now ~1800 users on meek-google sharing 8 Mbits. Of course, it's also possible that many are lurking. I wonder if we should think of a way to load-balance the CDNs a bit more, assuming Azure is accessible from China. Perhaps we could re-order or at least clarify the bridge options in the Tor Browser. Since it's logistically challenging to get bridges from inside a censored country, it's possible that users try the various bridge options using the built-in bridges (which are likely blocked) before discovering that meek works, so they use that. I wonder how we could encourage users to use other transports that are likely faster, then use meek as a last resort.
Azure is accessible in China but it's even more severely rate limited because it's more expensive than Google. We still have support from Google, so that $561.29 actually costs about $61.29.
I think you're right that people are choosing meek because it works without any setup. We have a kind of long-term goal to do a domain-fronted interface to BridgeDB, so that people could get obfs4 bridges automatically and directly within Tor Launcher. https://bugs.torproject.org/16550
On 01/11/2016 02:42 PM, David Fifield wrote:
We still have support from Google, so that $561.29 actually costs about $61.29.
Oh, I was not aware of this. When does the support expire, and how much would it cost (in terms of Tor's budget) to double the bandwidth to 16 Mbits, for instance? I'm just thinking about the implications if there were donations for meek.
On Mon, Jan 11, 2016 at 02:51:12PM -0900, Jesse V wrote:
On 01/11/2016 02:42 PM, David Fifield wrote:
We still have support from Google, so that $561.29 actually costs about $61.29.
Oh, I was not aware of this. When does the support expire, and how much would it cost (in terms of Tor's budget) to double the bandwidth to 16 Mbits, for instance? I'm just thinking about the implications if there were donations for meek.
It expires pretty soon. March, I think?
I don't know how much usage will increase with a higher rate limit, but I'm sure that we could saturate 24 Mbps, because that's about where we were before instituting rate limiting. I think of it the other way: rather than picking a speed and figuring out what it will cost, set a cost and then adjust your speed to meet it.
On 01/11/2016 12:47 PM, David Fifield wrote:
December 2015 $561.29 + $603.27 + $172.60 = $1337.16 ... The number of users increased by about 1,000 in December 2015.
Thanks for the report, David.
There are now ~1800 users on meek-google sharing 8 Mbits. Of course, it's also possible that many are lurking. I wonder if we should think of a way to load-balance the CDNs a bit more, assuming Azure is accessible from China. Perhaps we could re-order or at least clarify the bridge options in the Tor Browser. Since it's logistically challenging to get bridges from inside a censored country, it's possible that users try the various bridge options using the built-in bridges (which are likely blocked) before discovering that meek works, so they use that. I wonder how we could encourage users to use other transports that are likely faster, then use meek as a last resort.
-
David Fifield -
Jesse V