Assuming they already own a PC, if someone buys two 3090 for it they’ll probably also have to upgrade their PSU so that might be worth including in the budget. But it’s definitely a relatively low cost way to get more VRAM, there are people who run 3 or 4 RTX3090 too.

For LLMs it entirely depends on what size models you want to use and how fast you want it to run. Since there’s diminishing returns to increasing model sizes, i.e. a 14B model isn’t twice as good as a 7B model, the best bang for the buck will be achieved with the smallest model you think has acceptable quality. And if you think generation speeds of around 1 token/second are acceptable, you’ll probably get more value for money using partial offloading.

If your answer is “I don’t know what models I want to run” then a second-hand RTX3090 is probably your best bet. If you want to run larger models, building a rig with multiple (used) RTX3090 is probably still the cheapest way to do it.

Is max tokens different from context size?

Might be worth keeping in mind that the generated tokens go into the context, so if you set it to 1k with 4k context you only get 3k left for character card and chat history. I think i usually have it set to 400 tokens or something, and use TGW’s continue button in case a long response gets cut off

llama.cpp uses the gpu if you compile it with gpu support and you tell it to use the gpu…

Never used koboldcpp, so I don’t know why it would it would give you shorter responses if both the model and the prompt are the same (also assuming you’ve generated multiple times, and it’s always the same). If you don’t want to use discord to visit the official koboldcpp server, you might get more answers from a more llm-focused community such as !localllama@sh.itjust.works

A static website and Immich

It sucks when this happens, but the article also says:

Update 20/11/23 14:33 UTC — Crytek responded to note: “This is a known issue and we are working on it to fix it and apply the fix for the resolution as soon as possible.”

So not ideal but at least the devs want to support Linux.

And you’re 100% sure you installed it in the correct wine prefix? Because that’s the tricky part, and having it installed in a different wine prefix won’t work.

I had the same “unable to detect uplay” error except for a different Anno game. Here’s how I solved it, if you want to try:

• Install ProtonUp-Qt, then add SteamTinkerLaunch using it.
• In Steam, go to Properties… for the game that needs Ubisoft Connect. Then Compatibility tab, check “Force the use of a specific Steam Play compatibility tool”, and select “Steam Tinker Launch” from the dropdown.
• Start the game, and quickly press the “MAIN MENU” button at the bottom of the window.
• Click “One time run”, choose the UbisoftConnectInstaller.exe that you downloaded and click “RUN COMMAND”

There are tons of options for running LLMs locally nowadays, though none come close to GPT4 or Claude 2 etc. One place to start is /c/localllama@sh.itjust.works

Static html+css page generated with this: https://github.com/maximtrp/tab

Do you mean that you want to build the docker image on one computer, export it to a different computer where it’s going to run, and there shouldn’t be any traces of the build process on the first computer? Perhaps it’s possible with the –output option… Otherwise you could write a small script which combines the commands for docker build, export to file, delete local image, and clean up the system.

https://github.com/miroslavpejic85/mirotalk might be an option. There’s both a server based version and a p2p version IIRC.

I asked someone about this a few days ago, and they claimed to have over 30000 photos in Nextcloud without issues

I suppose “a few” is quite open to interpretation, but I have 50k photos now so if it can handle 100k without getting sluggish it’ll probably be fine for the foreseeable future.

Does Nextcloud handle large numbers of photos nowadays? IIRC when I was comparing programs some years ago I read that both it and Owncloud struggled when you got to a few 10000s of photos.

Ah, nice.

Btw. perhaps you’d like to add:

build: .

to docker-compose.yml so you can just write “docker-compose build” instead of having to do it with a separate docker command. I would submit a PR for it but I have made a bunch of other changes to that file so it’s probably faster if you do it.

Awesome work! Going to try out koboldcpp right away. Currently running llama.cpp in docker on my workstation because it would be such a mess to get cuda toolkit installed natively…

Out of curiosity, isn’t conda a bit redundant in docker since it already is an isolated environment?