Re: [tor-bugs] #13089 [Onionoo]: use an embedded web server/servlet engine for Onionoo

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#13089: use an embedded web server/servlet engine for Onionoo
-----------------------------+-----------------
     Reporter:  iwakeh       |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  minor        |  Milestone:
    Component:  Onionoo      |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by karsten):

 Replying to [comment:4 iwakeh]:
 > Replying to [comment:3 karsten]:
 > > I surely wouldn't mind other people to run their own instances of
 Onionoo.  For example, I'd love to see you running one and have Onionoo
 clients list that as fallback alternative if onionoo.torproject.org is
 down.
 > Running my own Onionoo server? Hmm, never occured to me ...
 > The only big hindrance is that I don't have the means for hosting it.
 > But, maybe I can find some free hosting.

 Okay.  Maybe we can figure something out.

 > > Though I'm not sure if this ticket is the main barrier, because the
 real trick is to initialize a new Onionoo instance with years of Tor
 network archives.  But that shouldn't stop us here.
 > How many GB/TB approximately?

 The current system uses 33G of its 242G, but you'll need even more for
 initialization.  500G maybe?

 > > ... Let's make it easier to configure and deploy Onionoo, regardless
 of how many instances there will be.
 > Yeah, that'll be helpful for testing, too.
 >
 > > Which of the three (embedded Tomcat, Jetty, Netty) should we try out,
 and why?  And would you be willing to submit a patch?
 > Sure, I'd like to submit a patch.
 > I would aim at making the change independent of the actual choice of
 server, well, as far as possible.
 > Switching the (embedded or not) server should always be possible, just
 in case something
 > better comes along ...

 Sure, the fewer changes are necessary to switch back or to a different
 embedded server solution, the better.

 > I mentioned testing above. Do you have any kind of benchmark for
 Onionoo?
 >
 > Criteria for choosing the embedded server could be
 > * easy integration (i.e. none or hardly any coding overhead)
 > * performance (according the to-be-determined benchmark)
 > * ease of configuration

 There's no benchmark yet, but we might be able to come up with something.
 I could try to extract distributions of requested document types and
 parameters from current access logs, and then we measure how many requests
 each of the variants can handle in a given amount of time.

 Is there a tool for this, or are we building the tool while performing the
 measurements?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13089#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs