[tor-bugs] #9529 [Tor Check]: Replace check.tp.o webservers with Arlo's Go version

[Tor Bug Tracker & Wiki]

#9529: Replace check.tp.o webservers with Arlo's Go version
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:     
     Type:  task       |         Status:  new
 Priority:  normal     |      Milestone:     
Component:  Tor Check  |        Version:     
 Keywords:             |         Parent:     
   Points:             |   Actualpoints:     
-----------------------+----------------------------------------------------

Comment(by phobos):

 exitlist/tordnsel is a separate piece of software which can be run
 standalone on various servers. Bridgedb probably should run its own copy,
 rather than rely on a central server.

 As for check.tpo website, it shouldn't exist at all. The functionality of
 it should be moved to the browser, ala TBB 3.x. Over the life of
 check.tpo, we've replaced perl with python, and apparently are ready to
 replace python with go. We keep re-writing the same bad architecture in
 the cool language of the day. And to be clear, the bad architecture is to
 have the entire tor browser userbase hit a single website to learn "tor or
 not".

 All that being said, the basic questions about this go implementation are
 around scaling. We seem to sustain 40-70 requests per second throughout
 the day[1]. We peak at 500 requests per second on really busy times, such
 as last week when check went down.  Can Arlo's code handle this? How much
 memory is consumed on average? How many cpu cores does it need to handle
 all of this?  Or is the answer to deploy it and find out?

 [1]
 https://munin.torproject.org/torproject.org/sergii.torproject.org/index.html#apache

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9529#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online