[tor-bugs] #10192 [Pluggable transport]: websocket-server seems to be (very) slow

[Tor Bug Tracker & Wiki]

#10192: websocket-server seems to be (very) slow
-------------------------------------+-------------------------------
     Reporter:  Aymeric              |      Owner:  asn
         Type:  defect               |     Status:  needs_information
     Priority:  normal               |  Milestone:
    Component:  Pluggable transport  |    Version:
   Resolution:                       |   Keywords:
Actual Points:                       |  Parent ID:
       Points:                       |
-------------------------------------+-------------------------------
Changes (by dcf):

 * status:  new => needs_information


Comment:

 Replying to [ticket:10192 Aymeric]:
 > After multiple tests and iterations, here is the average behavior with
 tor1.bamsoftware.com with the following configuration:
 >
 > Browser (2 Mbps) --> 600kbps --> tor1 300 kbps --> Tor 2 Mbps --> ORDB
 (400/500 kbps) --> Tor 2 Mbps --> 2 Mbps --> Browser (2Mbps) (real:
 300kbps)

 Thanks for this report. I don't understand your testing setup? Are you
 using a browser as a WebSocket client?

 For a pure bandwidth measurement, you should try the
 [https://gitweb.torproject.org/pluggable-
 transports/websocket.git/tree/HEAD:/src/websocket-client websocket-client]
 program; otherwise, you may actually be measuring something in a browser.

 Also, I recommend setting up a relay on localhost so you can see the log
 output, and look for these messages in websocket-server.log:
 {{{
 "frame payload length of %d exceeds maximum of %d"
 }}}
 I can imagine that too many of those would cause it too look like a slow
 connection. Running it locally will also allow you to check if CPU usage
 becomes too high.

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