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

Very slow IO with WSL2 even on SSD. Example: updatedb #4668

Closed
danielniccoli opened this issue Nov 12, 2019 · 2 comments
Closed

Very slow IO with WSL2 even on SSD. Example: updatedb #4668

danielniccoli opened this issue Nov 12, 2019 · 2 comments

Comments

@danielniccoli
Copy link

danielniccoli commented Nov 12, 2019

  • Your Windows build number: Microsoft Windows [Version 10.0.19018.1]
  • What you're doing and what's happening:

WSL 2 installed on a SSD. Running updatedb.
It takes 6 minutes the first time and 2 minutes the second run. On an SSD this should take a couple of seconds at most, at least for the second run.

root@BORKASON:~# time updatedb

real    5m50.360s
user    0m7.647s
sys     0m50.115s
root@BORKASON:~# time updatedb

real    1m55.429s
user    0m2.723s
sys     0m16.396s

  • What's wrong / what should be happening instead:
    On an SSD this should take a couple of seconds at most.
@onomatopellan
Copy link

Try adding /mnt to the PRUNEPATHS variable in /etc/updatedb.conf

Accessing /mnt files in WSL2 is slow right now #4197

@therealkenc
Copy link
Collaborator

therealkenc commented Nov 13, 2019

Try adding /mnt to the PRUNEPATHS variable in /etc/updatedb.conf

That's the catch. I didn't consider updatedb(8) would traipse all over /mnt (an strace log would have made that obv). Thanks!

[late ed] Odd though. Having something big and slow on /mnt in Real Linux isn't an unusual scenario; I have a slow USB backup drive on mine. "Forgetting" (scare quote) to tweak /etc/updatedb.conf is probably pretty common too. Never seen it take 5min tho.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants