search

SociallyIneptWeeb / LanguageLeapAI

Your Personal Multilingual AI Translator
MIT License
843 stars 171 forks source link

Update Readme.md to include wsl --shutdown | And also made a one click install script in releases page #73

Closed stancho44 closed 1 year ago

stancho44 commented 1 year ago

Having wsl and docker will eat up about 32 gb of ram when I tested it. This will close wsl and clear the memory usage from the program. The end user also could restart their computer to fix but it is not ideal.

SociallyIneptWeeb commented 1 year ago

Is this for only after you are done using the program?

stancho44 commented 1 year ago

After stopping the docker containers with the down command. Docker will continue to hog memory in the process vmmem.exe in task manager. I've included the wsl shutdown command in the readme file just to help people reduce the ram. As you can see by the screenshots I've provided, the ram is being used and when using the docker-compose down it frees up some ram but is not deallocated completely until I run the wsl --shutdown command.

And yes this is after you shutdown the application. The only issue I'm running now is that you can't start up the program until you stop docker desktop.

image image image

stancho44 commented 1 year ago

I've also added a one-click install bat script in the releases tab just to make the process simpler and it should work on most systems. Tested via windows sandbox.

stancho44 commented 1 year ago

I suggest scrapping the idea and stopping the docker service using the wsl --shutdown command. Closing the docker service from the task tray does a similar thing but slowly. The downside to the old method is that the user has to restart the docker service to launch the docker service again. In this method, the user stops the docker desktop and starts the docker desktop to run the program again.