[-] xcjs@programming.dev 1 points 1 year ago

Awesome! Let me know how it works for you!

[-] xcjs@programming.dev 1 points 2 years ago

I agree with this, especially because this hasn't pushed any discussion forward about federal level consumer privacy laws in the United States.

[-] xcjs@programming.dev 1 points 2 years ago

Pixel Experience is unfortunately dead now. 🙁

[-] xcjs@programming.dev 1 points 2 years ago

They added a video player with version 3, I think.

[-] xcjs@programming.dev 1 points 2 years ago

We all mess up! I hope that helps - let me know if you see improvements!

[-] xcjs@programming.dev 1 points 2 years ago* (last edited 2 years ago)

I think there was a special process to get Nvidia working in WSL. Let me check... (I'm running natively on Linux, so my experience doing it with WSL is limited.)

https://docs.nvidia.com/cuda/wsl-user-guide/index.html - I'm sure you've followed this already, but according to this, it looks like you don't want to install the Nvidia drivers, and only want to install the cuda-toolkit metapackage. I'd follow the instructions from that link closely.

You may also run into performance issues within WSL due to the virtual machine overhead.

[-] xcjs@programming.dev 1 points 2 years ago

Ok, so using my "older" 2070 Super, I was able to get a response from a 70B parameter model in 9-12 minutes. (Llama 3 in this case.)

I'm fairly certain that you're using your CPU or having another issue. Would you like to try and debug your configuration together?

[-] xcjs@programming.dev 1 points 2 years ago

Exactly why I surmised they may not want to keep it there: https://programming.dev/comment/8019112

[-] xcjs@programming.dev 1 points 2 years ago

I think I'm going to take your advice on this. It's driving me insane and my attempted solution did not work.

[-] xcjs@programming.dev 1 points 2 years ago* (last edited 2 years ago)

Nope - I'm still having the issue. I'm going to follow the advice I received here to file an issue.

[-] xcjs@programming.dev 1 points 2 years ago* (last edited 2 years ago)

Alright, so I think I may have solved it. I reset Rider to its default settings, and it worked at least once. I'll try again later to confirm that was the fix.

view more: ‹ prev next ›

xcjs

0 post score
0 comment score
joined 3 years ago