xcjs @ xcjs @programming.dev

Posts

0

Comments

100

Joined

2 yr. ago

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

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.

Good luck! I'm definitely willing to spend a few minutes offering advice/double checking some configuration settings if things go awry again. Let me know how things go. :-)

It should be split between VRAM and regular RAM, at least if it's a GGUF model. Maybe it's not, and that's what's wrong?

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?

Unfortunately, I don't expect it to remain free forever.

No offense intended, but are you sure it's using your GPU? Twenty minutes is about how long my CPU-locked instance takes to run some 70B parameter models.

On my RTX 3060, I generally get responses in seconds.

It's a W3C managed standard, but there are tons of behavior not spelled out in the specification that platforms can choose to impose.

The standard doesn't impose a 500 character limit, but there's nothing that says there can't be a limit.

Or maybe just let me focus on who I choose to follow? I'm not there for content discovery, though I know that's why most people are.

That's the funny thing about UI/UX - sometimes changing non-functional colors can hurt things.

At some point, you lose productivity and reduced work weeks have shown increases in productivity can happen.

My go-to solution for this is the Android FolderSync app with an SFTP connection.

I'm not familiar with creating fonts specifically, but you'll want to commit any resources necessary to recreate the font file, including any build scripts to help ease the process and instructions specifying compatible versions of tooling (FontForge in this case). Don't include FontForge in the repository, of course.

The compiled font files should be under releases in GitHub for the repository.

Git isn't generally meant for binary resources but as long as they're not too large, they'll be fine. You just may not have meaningful ways to compare changes easily.

I mean, sysvinit was just a bunch of root-executed bash scripts. I'm not sure if systemd is really much worse.

Systemd was created to allow parallel initialization, which other init systems lacked. If you want proof that one processor core is slower than one + n, you don't need to compare init systems to do that.

Correction: migrated to GitLab, but I don't expect they'll want to keep it there.

The Nuzu repository is already wiped.

With UI decisions like the shortcut bar, they really don't. I switched to another SMS app because I couldn't stand it.

I've been disappointed in general with the XPS line in recent years. Dell has made some keyboard changes that I am not a fan of:

• A touch bar instead of function keys? Why? Did they not learn from Apple's mistake?
• Changing Fn + Left to Page Down instead Home? And Fn + Right to Page Up instead of End? Once again, why?

I've been purchasing the XPS line of laptops since 2013, but I stopped as soon as those changes landed and the Developer Edition of their laptops shipped with inferior hardware compared to the Windows ones.

On Android, it moved SMS messages from the shared SMS store upon receipt and to Signal's own database, which was more secure.