It works in reverse too. You can make any LLM “forget” that it is even able to refuse anything.
It works in reverse too. You can make any LLM “forget” that it is even able to refuse anything.
Definitely. It has some alignment, but it won’t straight up refuse to do anything. It will sometimes add notes saying that what you’ve asked is kinda maybe against the law, but will produce a great response regardless. It’s a 70b, so running it locally is kind of a challenge, but for those who can run it - there is simply no other LLM that you can run at home that gets even close to it. It follows instructions amazingly, it’s very consistent and barely hallucinates. There is some special mistral sauce in it for sure, even if it’s “just” a llama2-70b.
The info in this thread is mostly incorrect - error has nothing to do with the SD card you plug in the server.
This error happens because HP had a bug in earlier versions of iLo where flash memory wear levelling was not enabled. It results in a failed flash chip unless iLo was updated early on.
The SD card is Embedded - it’s NOT the one that you plug in, but rather it’s soldered down on the motherboard. You can try formatting it (there is HP support advisory on this, requires sending special XML) but chances of bringing it back to life are slim. Out of 10+ machines with these symptoms I’ve seen only two were alright after flash format. Proper fix would be to desolder and replace the chip on the motherboard…
Part number for the chip: SDIN7DP2-4G
Here’s the link to support advisory: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04996097
It’s marginally better than original but WAYY more censored. It is pretty intrusive. It refused to write a bash script to kill a process by regexp 🤦
There is a bit of a conundrum here: in order to run a model that is any good in coding you want it to have a lot of parameters (the more the better) but also since it’s code and not some spoken language - precision matters here. Home hardware like 3090 is able to run ~30b models, but there is a catch - it just fits and only in quantized form = with 4x worse precision typically. Unless we see some breakthrough here that makes inference of huge models possible at full precision - the hosted AI will always be better for coding. Not saying such breakthrough is impossible though - quite the opposite in my opinion.
I’ve got a k80 and it’s… underwhelming.
I does run 30B models tho. And it is cheap.
They’re trying to kill off competition right now. Once everyone tied their systems to their API they’re gonna jack these prices right up. Or soft-force everyone onto more expensive GPT-4.
LOL “instead” :-D They are surely targeting both Twitter AND some John Pantswearer from Nebraska who downloaded “Despacito.mp3” too. Lawyers be lawyering.
It’s not the model that would be sending telemetry - it’s the runtime that you load it up in. Ollama is open source wrapper for llama.cpp, so (if you have enough patience) you could inspect the source code to be sure. Regarding running it in sandbox: you could, and generally it does not add any tangible overhead to the tokens per second performance, but keep in mind that in order to give the model runtime (ollama, vllm and the like) access to your GPU you usually need some form of sandbox concessions like PCIe passthrough for VMs or running nvidia’s proprietary container runtime plugin. From my measurements, there is zero difference in performance when running a model loaded in a GPU on baremetal, a docker container with nvidia container runtime or a proxmox VM with PCIe passthrough. Model executes on GPU itself and barely uses any CPU (sampling and loras are usually CPU operations). vLLM does collect anonymized usage stats. Since it’s open source - you can actually see what’s being sent (spoiler: it’s pretty boring). As far as I know, Ollama has nothing like that. None of the open source engines that I know of are sending your full prompts or responses anywhere though. It doesn’t mean they will keep being like that forever or that you should be less vigilant though 👍