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

High network connection delay when using mirrored networking using "localhost" #11186

Open
1 of 2 tasks
mio9 opened this issue Feb 20, 2024 · 2 comments
Open
1 of 2 tasks
Labels

Comments

@mio9
Copy link

mio9 commented Feb 20, 2024

Windows Version

Microsoft Windows [Version 10.0.22621.3155]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.133.1

Distro Version

Arch Linux / OpenSUSE-Tumbleweed (distro independent)

Other Software

No response

Repro Steps

[General method]

  1. Start a web server that serves a lot of small files inside WSL (more pronounced with 500+ files)
  2. Make a frontend that loads all those files
  3. Observe the insanely slow loading

[My specific case]

  1. Start a nuxt3 dev server inside WSL with sufficient amount of plugins and extensions installed in nuxt
  2. Access the dev server using "localhost:[port]"
  3. Observe the insanely slow loading / download of all assets
  4. Access the same dev server using "127.0.0.1:[port]"
  5. Observe the blazing fast loading / download speed

Expected Behavior

Using 127.0.0.1 and localhost should yield the same "loopback" instant response

Actual Behavior

Using localhost imposes heavy delay for each request/connection handled as if something is severely overloaded

Diagnostic Logs

A webapp served by Nuxt dev server, loaded within 3 seconds when browsed using 127.0.0.1
image

The same webapp, took a whole 30 seconds when using localhost
image
Every download takes 300ms for initial connection, stalling every other downloads behind, even the download itself takes just 1ms
image

Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@mio9
Copy link
Author

mio9 commented Feb 20, 2024

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Not the same. Connection here is not timed out, but simply having a fixed 300ms initial connection delay for everything connecting through the "localhost" hostname

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