-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High CPU occupancy #26
Comments
Here's a part of perf report showing below. In this report, we can find that
|
It occurs at ss-server report TCP connection timeour. |
I found the solution, finnaly. Patch's on the way in 24hr (after I finish golang learning, OMG) |
I have also found this issue happens frequently and get back to use the old version 464a11e. |
It's weird.
@cbeuw Are you using go 1.9? |
@kimw Yes. I was using go 1.10. The issue occurs only for the version after supporting TFO. Edit: go 1.9 works perfectly. I think the issue might be related to the compatibility of TFO library with go 1.10. |
@linusyang Yes, it's occured by Go TFO. Cause the go lang is not support TFO at all, (it keep delay since 1.8, 1.9 ... and addressed maybe will support in 1.11), all the TFO patches are running on the dark side, go lang offical libs are changing w/o thinking of it. The patch cat said, she's tired :) The upstream, Go TFO, supports go 1.8 & 1.9 only. I'm tring to do some work on go 1.10, you know I'm a golang newbie, I work with manual...so, don't trust me. Anyway, the solution I told earler is to dirty hack a connection timeout on shadowsocksToRemote(). It's a double side sword. The timeout saves the CPU but cut off connections forcely. Sigh! |
@kimw I really hope the go team can incorporate TFO ASAP. I may use syscall for all socket operations if this becomes too inconvenient. |
Anyway, it's do work on go 1.9 now. We can release it under this condition. go 1.10 will be supported on next release or never supported ;) EDIT, @cbeuw BTW, can you manage the release version? To be honest, I personally feel kind of mess. Sorry for the words. |
@kimw |
|
Closed cbeuw/gotfo@9f0986e |
@cbeuw I try to step into |
@kimw |
As I known there're two kind of redirections,
Web browser <==> gq-server <==> HTTPD server
I name it as HTTP REDIR. It was fixed in Fix High CPU occupancy #13.
ss-local <==> gq-client <=> gq-server <=> ss-server
I name it as SS REDIR. Maybe need some kind of fix?
The text was updated successfully, but these errors were encountered: