Q: I use Devkinsta to create my local site in my website at 09/26/2022, but the local site is too slow to edit my website! I think the local site will be very fast to give any change test in the website! A:
Q: DevKinsta Version2.8 A:
Q: OS Version I’m not sure how to find the Os version. A:
Q: Docker Desktop Version4.12.0 A:
Q: Were any error codes or messages observed? If so, what were they? A:
So if your Windows version supports Hyper-V and you have enabled virtualization, I recommend DELETING your site within DevKinsta before you switch to Hyper-V. This is because you will not be able to access a site created using WSL2 after switching to Hyper-V.
Once you have deleted your sites you just need to open Docker Desktop and click on the “Troubleshoot” button at the top:
Under “General” you will need to uncheck the “Use the WSL 2 based Engine” box then “Apply & Restart”
So our developers are going to try to modify the way the site files are stored on local systems so DevKinsta will eventually be faster even on WSL2 without changes. Usually WSL2 IS faster than Hyper-V but since Docker is accessing site files directly from Windows, a delay occurs/leads to slowness.
Thank you Kevin,
I’m not good at this system settings, and I don’t have so much time to test these options.
In my situation, it’s faster to use kinsta’s cloud staging environment to update and test my website.
It’s really a very slow local site in my experience.
And I hope kinsta team can provide a fastest solution than flywheel did as faster as you can.
The solution to this issue is really straight forward and has been for a really long time, but for whatever reason DevKinsta is not prioritizing it’s implementation. The lag is introduced by accessing the windows file system from WSL2. The solution is to allow storing site files in WSL2, which is straight forward as they resolve to a network path \\wsl$\ however they do not let you change the file directory to this and thus the slowdown.