[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #21312 [Obfuscation/Snowflake]: snowflake-client is pegged at 100% cpu



#21312: snowflake-client is pegged at 100% cpu
-----------------------------------+--------------------------
 Reporter:  arlolra                |          Owner:  arlolra
     Type:  defect                 |         Status:  assigned
 Priority:  High                   |      Milestone:
Component:  Obfuscation/Snowflake  |        Version:
 Severity:  Major                  |     Resolution:
 Keywords:                         |  Actual Points:
Parent ID:                         |         Points:
 Reviewer:                         |        Sponsor:
-----------------------------------+--------------------------

Comment (by dcf):

 Replying to [comment:24 arlolra]:
 > > A similar patch for the go proxy (which I have)
 >
 > https://gitweb.torproject.org/pluggable-
 transports/snowflake.git/commit/?id=ff8f3851082e8f7f8b4c8b99b161be35020aeb67

 Here are graphs of memory and file descriptor usage on the server hosting
 6 proxy-go instances, before and after deploying the patch. (Memory is
 systemwide, file descriptors are only for proxy-go processes.)

 It's pretty obvious the patch fixed a memory leak. It looks like unlike
 snowflake-client, file descriptors were not a problem for proxy-go.

 I put a ruler for 10 hours because the proxy-go instances are restarted
 periodically, at intervals of 1, 2, or 10 hours (two instances for each
 interval). The periodic restarting was a workaround for them not working
 if you let them run too long).

 [[Image(proxy-go-mem.20180308.png)]]

 [[Image(proxy-go-fd.20180308.png)]]

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21312#comment:25>
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