[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):

 Replying to [comment:5 mccajm]:

 > 500 req/s seems like an _easily_ achievable number.  Although all
 software is different, we've benchmarked similar go services up to 65k
 req/s.  That used 15% of a core and a few hundred MB of RAM.  I need to
 read TorCheck.py further to understand what I'm missing, but from speaking
 to arma the current problems seems to be the wait time: to spawn a cgi
 process and iowait for things like dns.  Is the current Apache compiled
 with a modified MAX_CLIENTS?  If the connections are taking longer than a
 second, Apache will only be able to handle 255 simultaneous connections.

 We run wsgi in daemon mode, which pre-spawns 50 python processes along
 with 40 threads per process. There is no cgi load time per request. From
 looking at the server when it's busy, torcheck.py is the bottleneck, not
 apache nor tordnsel. Tordnsel typically returns answers in 0.03 seconds.
 We haven't tried debugging torcheck.py to see what's so slow inside it.

 The current apache is stock debian, we don't compile software on and for
 production machines. Generally, if it's not in debian nor torproject
 repos, we don't want to run it.  Apache on the machine can handle 800
 maxclients using the worker mpm model.

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