Skip to content
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

Weird Lantency Problem #93

Closed
clowwindy opened this issue Apr 18, 2014 · 2 comments
Closed

Weird Lantency Problem #93

clowwindy opened this issue Apr 18, 2014 · 2 comments
Assignees
Labels

Comments

@clowwindy
Copy link
Contributor

time curl -v --socks5-hostname 127.0.0.1:1080 http://www.google.com/ >/dev/null

libev local + nodejs server = 200ms
nodejs local + nodejs server = 260ms
libev local + libev server = 340ms
nodejs local + libev server > 500ms

libev local with nodejs server is fast, others are slow.

Problems may exist in nodejs local and libev server.

@clowwindy
Copy link
Contributor Author

  else cachedPieces.push data  if stage is 4
  # remote server not connected
  # cache received buffers
  # make sure no data is lost

->

  else if stage is 4
    if not remote?
      connection.destroy() if connection
      return
    data = encryptor.encrypt data
    connection.pause() unless remote.write(data)

@madeye
Copy link

madeye commented Apr 18, 2014

If the dest addr in the header is hostname, shadowsocks-libev has a minimum 200ms latency.

clowwindy added a commit that referenced this issue Apr 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants