Filesystem Feature and Performance Issues

[atrauzzi]

Submitted as per a twitter convo with @craigloewen-msft.

Please fill out the below information:

• Your Windows build number: Microsoft Windows [Version 10.0.18975.1000]

• What you're doing and what's happening: In my particular case, I'm running the phpstorm IDE pointed at my wsl$\Ubuntu share, mapped as W:.
  Over the course of using my WSL2-backed share, I receive warnings and experience very obvious performance degradation of static code analysis in the IDE. I also am always shown the following notification on first run:

• What's wrong / what should be happening instead: I think static code analysis features should not be impacted by the fact that I'm using a share that - while it uses network-based technologies - is effectively on the same physical machine as my IDE.

[therealkenc]

wsl2 perf on 9p is #4197
inotify(7) on 9p is #4224, #4064, tangential #1956 (message), others. (Yes, "they are under a network mount.")
rename(2) on 9p is #1529
readlink(2) on 9p is #4104

If your heart is set on JetBrains, drawing outside the lines and using VcXsrv or xrdp is a route though, just like is was with VS Code before WSL Remote was invented.

[atrauzzi]

Sorry, I'm not sure I followed that last paragraph?

[therealkenc]

I decorated the paragraph with links with more information. It is possible in extremis to use native Linux JetBrains PhpStorm, just as you would in a VM like Hyper-V/VirtualBox/QEMU, or as you would remotely from a headless cloud server. It isn't a supported scenario; at least in the sense that those third-party X server products aren't WSL actionable. But that doesn't stop lots of folks.

The current recommended practice ref #4169 (message) per this blog post is to access files on the WSL (Linux) side. Recent versions VS Code now does this by running a service on WSL (Real Linux too). But that is small consolation if your development environment isn't Code, natch.

[atrauzzi]

So is the message here to not expect to use the WSL2 share because it will never offer native performance and features?