[tor-dev] Summary of meek's costs, June 2015
David Fifield
david at bamsoftware.com
Mon Jul 6 16:03:44 UTC 2015
Here's the summary of meek's CDN fees for June 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
--
total by CDN $4765.72 + $5509.18 + $0.00 = $10274.90 grand total
The rate limiting of meek-google and meek-amazon has been partially
effective in bringing costs down. The bill this month is the lowest it
has been since February. I aimed to get the meek-google bill down to
$500, the amount of the monthly grant we're getting from Google, and it
came in a little above that. meek-amazon, on the other hand, did not
decrease much at all. I think it may be because of Amazon's per-request
billing.
The number of users was pretty stable, staying mostly in the range
3000–4500.
https://metrics.torproject.org/userstats-bridge-transport.html?graph=userstats-bridge-transport&start=2015-04-01&end=2015-06-30&transport=meek
If you want to set up your own bridge and CDN instance without rate
limiting, I can help you do it. 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 ==
Rate limiting brought down bandwidth usage almost 50%. Despite that,
instance hours went up. The rate limiting happens at the bridge, so it's
possible that requests are taking longer to process at the App Engine
level, requiring more instance hours.
Here is how the Google costs broke down:
2807 GB $336.87
5299 instance hours $264.96
Compared to the previous month:
5359 GB $643.07
4571 instance hours $228.57
https://globe.torproject.org/#/bridge/88F745840F47CE0C6A4FE61D827950B06F9E4534
== Amazon a.k.a. meek-amazon ==
Bandwidth use was down about 16% compared to the previous month. The
number of requests stayed about the same.
As you can see, the major contributor to the Amazon bill is not
bandwidth but the number of requests. I hope this ticket will help
reduce the number of requests we make:
"Use streaming downloads"
https://trac.torproject.org/projects/tor/ticket/12857
Asia Pacific (Singapore) 114M requests $136.84 831 GB $111.35
Asia Pacific (Sydney) 845K requests $1.06 2 GB $0.40
Asia Pacific (Tokyo) 57M requests $68.43 336 GB $43.11
EU (Ireland) 184M requests $221.41 1454 GB $108.52
South America (Sao Paulo) 8M requests $18.87 53 GB $12.54
US East (Northern Virginia) 64M requests $64.23 422 GB $33.25
--
total 429M requests $510.84 3101 GB $309.17
https://globe.torproject.org/#/bridge/3FD131B74D9A96190B1EE5D31E91757FADA1A4F3
== Azure a.k.a. meek-azure ==
meek-azure bandwidth use continues to increase, up 17% compared to the
previous month. Keep in mind that our grant expires in October, so you
should not count it continuing to work after that.
Speaking of the grant, they switched me over to a new kind of sponsored
account that will enable me to see the exact bandwidth use and what its
cost would be. That should be available starting next month. Until now,
we have had to estimate bandwidth usage by measuring at the bridge.
https://onionoo.torproject.org/bandwidth?fingerprint=AA033EEB61601B2B7312D89B62AAA23DC3ED8A34
Estimated bandwidth use this month:
2015-06 3038 GB
Compared to last month:
2015-05 2592 GB
https://globe.torproject.org/#/bridge/AA033EEB61601B2B7312D89B62AAA23DC3ED8A34
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
https://lists.torproject.org/pipermail/tor-dev/2015-June/008932.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: userstats-bridge-transport-meek-2015-04-01-2015-06-30.png
Type: image/png
Size: 13011 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150706/360e6f07/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: meek-google-88F745840F47CE0C6A4FE61D827950B06F9E4534-2015-06.png
Type: image/png
Size: 29839 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150706/360e6f07/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: meek-amazon-3FD131B74D9A96190B1EE5D31E91757FADA1A4F3-2015-06.png
Type: image/png
Size: 30311 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150706/360e6f07/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: meek-azure-AA033EEB61601B2B7312D89B62AAA23DC3ED8A34-2015-06.png
Type: image/png
Size: 44544 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150706/360e6f07/attachment-0007.png>
More information about the tor-dev
mailing list