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.
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.
I was reflecting on this myself the other day. For all my criticisms of Zuckerberg/Meta (which are very valid), they really didn't have to release anything concerning LLaMA. They're practically the only reason we have viable open source weights/models and an engine.
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.
I...do not miss XP, but I understand the nostalgia attached to it.
I learned a lot of technical skills on XP, but that's what made me appreciate the architectural decisions behind UNIX-likes all the more.
I'm using a combination of:
Is it possible that connecting to WiFi triggers app updates in the background? Those can be somewhat intensive especially when batched.
Additionally, the Google Play Store no longer notifies when app updates occur, so this process is a little more opaque than it used to be.
I'd say not because of those things but due to overall socioeconomic well-being.
It doesn't quite say that, but I think the meaning is essentially the same: "Don't choose a name after a project unique to that machine." - RFC 1178
For my homelab, I think that's fine to do. I'm unlikely to have multiple Plex servers locally, for example, and if so, numerically naming them is fine - I provision with Ansible, and if I'm at the point where I'm having sequentially numbered hosts, they'll be configured as cattle anyway. Also, having the names reflect the services a host provides makes it easier to match in my playbooks.
I think it's a better scheme than turning to mythology, fiction, or animal species, which oddly enough RFC 1178 does encourage you to do.
Show me a music store I can purchase music from on my phone through an app, and I'll purchase it.