[tor-bugs] #10192 [Pluggable transport]: websocket-server seems to be (very) slow
Tor Bug Tracker & Wiki
blackhole at torproject.org
Mon Nov 25 16:08:40 UTC 2013
#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: |
-------------------------------------+-------------------------------
Comment (by dcf):
Thanks again for following up on this report. But I still really can't do
anything with the information you've given me. Please ''stop testing
against tor1'' because that is full of confounding factors. You need to
run a copy of websocket-server on localhost, and see if it has the same
behavior. It's not hard to do—just run a copy of tor with a few lines of
configuration. There are instructions for doing it
[https://gitweb.torproject.org/pluggable-
transports/websocket.git/blob/HEAD:/README right here]. You might also
need to set `BridgeRelay 1` in your case.
Did you try [https://gitweb.torproject.org/pluggable-
transports/websocket.git/tree/HEAD:/src/websocket-client websocket-client]
yet, or not?
I'm asking you to do exactly the the same things I would have to do if I
were investigating a performance problem; the first thing I would do is
try running a copy of the server on localhost. Then I would check CPU
usage, profile the execution, and look at packet captures (again on
localhost). It's not that I doubt you—it's that doing these things will
take me hours and I'm not even sure what I'm looking for. If this issue is
important to you, you need to do some of the legwork.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10192#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list