Then I already have my tool and I don't have any use for a new one.Ah, but you do already if you're a Google user![]()
(Irrelevant, but I am trying to wean myself off Google services and move into self-hosting)
Then I already have my tool and I don't have any use for a new one.Ah, but you do already if you're a Google user![]()
Computers aren't things that can answer questions. Computers and software are tools, I see them in the same way I would see a screwdriver, knife or can opener. They're complex and they can do a lot more than a can opener, but at the end of the day, they're dumb tools, and I don't ask my knife the best way to cut an onion.
And yet, let it never be said that I don't try new things. Putting it on my to-do list today to play around with some models, maybe I'll see what the fuss is about.Ah, but you do already if you're a Google user
I agree, but you know how the tech world is anyway!
Let me know how it goes if you try it!
The most i find it useful for when coding is to generate snippets.
AI is bad at tying lots of things together, which UI does a lot of!
I feel a lot less confident if you're asking current AI to come up with answers on it's own, for questions which haven't been answered or even asked before. This is when their tendency to hallucinate becomes something you can't verify source material for.
This is why i only use LLMs that can cite sources. Everything needs to be confirmed. Especially when we're talking about uncommon knowledge.
Deepseek hallucinates things the least for me though, and the card up it's sleeve is that it often finds me a result that was probably on page 10 in Google.. or in a foreign language source ( which i can translate ).
I use deepseek as a first pass for research now, then follow up with independent websites or google to confirm.
it's been unable to unearth things i couldn't find on google, and get me to an ideal answer quicker. That's the value for me.

Self hosting seems far less something worth while for normal people, I mean he couldn't run the 'smart' model even with his setup ( let alone someone without a threadripper setup ).
edit: not to mention I wasn't even aware DS has a 'reasoning model' instead of 'predicting the next most used word'.
That is a step above, interesting. I will stop using Bing![]()

I currently run Qwen2.5-coder 14B ( Consumes ~8gb in GPU )
I don't have the rest of the answer it gave me, it was overly simplistic but acceptable. I was just following your advice, and asking a complex question, but my point was that I lost interest after it failed following its logic within the sentence. At hundreds of watts too, as you pointed it.How was the rest of the answer?
Please post result!
Steps to install:
I should get
in this GPU size ( very constrained )
That's to run the whole average human body. The brain itself is maybe 20% of that.The human brain runs on ~100w of power.
That's to run the whole average human body. The brain itself is maybe 20% of that.
That's to run the whole average human body. The brain itself is maybe 20% of that.
I am thinking, is there like a 'local assistant' type of llm which can integrate with calendar services ect ect? Having a personal assistant which doesn't run on some company server sounds very appealing. And if so, how large would it be? Would the generic
'chatbot / support' llm be viable as a personal assistant ( I always find those bots terribly limited, but they never tell you what they are based on )? And how hard would it be to write some kind of plugin to allow the llm to interact with other services?
Like with your code llm, could you integrate it into your workflow with automation: like tell it to 'update your github' and have it upload pending changes and generate changelog automatically based on annotations in your code?
My question is.... how accurate is it?
People expect me to be 98% accurate, i don't think 80% accurate is good enough!
Shouldn't be hard to set up automation using your own annotations, that's just parsing and not logic.
If you can get it to generate code based on a text input, how well can it translate a code snipet to human readable annotation?
And should this process be 100% reversible, where it generates the same code output based on an annotation, as it generates an annotation based on a code snippet? If it's not, but the answers are still correct, does this make the answer worth less ( because there is a variance, even if the intrinsic meaning stays the same ).
A 3060 would work ( My 4070 has 12gb )., it just won't be as quick.
With an Intel i5-10400 (6 cores, 12 threads) + RX 580 (4GB VRAM), you have a decent setup for running small LLMs with CPU+OpenCL acceleration.
Best Model Choices (4GB VRAM Limit)
- Tiny LLMs (Best Fit)
- Phi-2 (2.7B) – Efficient and should run smoothly.
- Llama 2 7B (4-bit) – Will run with CPU help.
- Mistral 7B (4-bit quantized) – Might work but will be slow.
- Optimized Inference Tools for OpenCL
- llama.cpp (has OpenCL support)
- KoboldCPP (for chat-based AI, supports OpenCL)
- Text-generation-webui (use CPU+OpenCL hybrid mode)
How to Run LLMs on Your Hardware
- Install llama.cpp (best OpenCL-compatible runtime)
- Download: GitHub - ggerganov/llama.cpp: LLM inference in C/C++
- Compile with OpenCL:
sh
KopiërenBewerken
make LLAMA_OPENCL=1- Run a quantized model (e.g., Phi-2):
sh
KopiërenBewerken
./main -m phi2-2.7b.Q4_K.gguf -t 6 -ngl 1- Use GGUF Models (Pre-Quantized for Small VRAM)
- Get 4-bit GGUF models from TheBloke on Hugging Face
- Load them with llama.cpp or KoboldCPP.
Performance Notes
Let me know if you want a detailed setup guide!
- RX 580 will help, but CPU will do most work
- Use 4-bit models to fit in VRAM
- Enable swap space if running out of RAM
![]()
Amberwolf said:Please give me a list (with url links to their codebase pages) of AIs (including LLMs) that I could run on an HP ProLiant DL380G6 48GB RAM non-networked server with a NVIDIA GeForce GTX 560 1GB PCIE video card.
Deepesssek said:Running modern AI models, especially large language models (LLMs), on an HP ProLiant DL380 G6 with 48GB RAM and an NVIDIA GeForce GTX 560 (1GB VRAM) is challenging due to the hardware limitations. The GTX 560 is an older GPU with limited VRAM, which restricts the size of models you can run. However, you can still run smaller AI models or optimized versions of larger models. Below is a list of AI models and frameworks that might be feasible on your hardware, along with links to their codebases:
---
### **1. GPT-NeoX (Smaller Models)**
- **Description**: GPT-NeoX is an open-source implementation of GPT-style models. You can run smaller versions of these models (e.g., 125M or 350M parameters) on your hardware.
- **Codebase**: [https://github.com/EleutherAI/gpt-neox](https://github.com/EleutherAI/gpt-neox)
- **Note**: Larger models like GPT-NeoX-20B will not fit on your GPU.
---
### **2. GPT-2 (Small Models)**
- **Description**: OpenAI's GPT-2 (small or medium versions) can run on your hardware. The 117M or 345M parameter models are suitable for your GPU.
- **Codebase**: [https://github.com/openai/gpt-2](https://github.com/openai/gpt-2)
- **Note**: Use the smaller models due to VRAM limitations.
---
### **3. LLaMA (Small Models)**
- **Description**: Meta's LLaMA models are efficient and can run on limited hardware. The 7B model might be too large, but smaller versions or quantized models could work.
- **Codebase**: [https://github.com/facebookresearch/llama](https://github.com/facebookresearch/llama)
- **Note**: Quantization (e.g., 4-bit or 8-bit) is recommended to reduce memory usage.
---
### **4. Alpaca-LoRA (Fine-Tuned LLaMA)**
- **Description**: Alpaca-LoRA is a fine-tuned version of LLaMA that uses Low-Rank Adaptation (LoRA) to reduce memory usage. It can run on lower-end hardware.
- **Codebase**: [https://github.com/tloen/alpaca-lora](https://github.com/tloen/alpaca-lora)
- **Note**: Requires quantization for your hardware.
---
### **5. BERT (Small Models)**
- **Description**: BERT is a transformer-based model for NLP tasks. Smaller versions like BERT-base or DistilBERT can run on your hardware.
- **Codebase**: [https://github.com/google-research/bert](https://github.com/google-research/bert)
- **Note**: Use the smaller variants for your GPU.
---
### **6. DistilGPT-2**
- **Description**: A distilled version of GPT-2 that is smaller and faster, making it suitable for limited hardware.
- **Codebase**: [https://github.com/huggingface/transformers](https://github.com/huggingface/transformers)
- **Note**: Available via Hugging Face's `transformers` library.
---
### **7. TinyBERT**
- **Description**: A compressed version of BERT designed for resource-constrained environments.
- **Codebase**: [https://github.com/huawei-noah/Pret...etrained-Language-Model/tree/master/TinyBERT)
- **Note**: Ideal for your hardware.
---
### **8. FastText**
- **Description**: A lightweight library for text classification and word embeddings. It runs efficiently on CPUs and does not require a GPU.
- **Codebase**: [https://github.com/facebookresearch/fastText](https://github.com/facebookresearch/fastText)
- **Note**: Does not require GPU.
---
### **9. Scikit-learn (Classical ML Models)**
- **Description**: For non-neural-network-based AI tasks, Scikit-learn provides a wide range of classical machine learning models.
- **Codebase**: [https://github.com/scikit-learn/scikit-learn](https://github.com/scikit-learn/scikit-learn)
- **Note**: Runs on CPU and does not require a GPU.
---
### **10. ONNX Runtime (Optimized Inference)**
- **Description**: ONNX Runtime allows you to run optimized versions of models. You can convert models to ONNX format and run them efficiently.
- **Codebase**: [https://github.com/microsoft/onnxruntime](https://github.com/microsoft/onnxruntime)
- **Note**: Useful for running quantized models.
---
### **11. TensorFlow Lite**
- **Description**: TensorFlow Lite is designed for running models on resource-constrained devices. You can use pre-trained models or convert existing ones.
- **Codebase**: [https://github.com/tensorflow/tenso...rflow/tensorflow/tree/master/tensorflow/lite)
- **Note**: Suitable for smaller models.
---
### **12. Hugging Face Transformers (Small Models)**
- **Description**: Hugging Face provides a wide range of pre-trained models, including smaller versions of popular architectures.
- **Codebase**: [https://github.com/huggingface/transformers](https://github.com/huggingface/transformers)
- **Note**: Use models like `distilbert`, `tiny-gpt`, or `mobilebert`.
---
### **13. Open Assistant (Small Models)**
- **Description**: Open Assistant provides smaller conversational models that can run on limited hardware.
- **Codebase**: [https://github.com/LAION-AI/Open-Assistant](https://github.com/LAION-AI/Open-Assistant)
- **Note**: Use smaller variants.
---
### **14. Stable Diffusion (Optimized Versions)**
- **Description**: For image generation, you can run optimized versions of Stable Diffusion (e.g., using `--lowvram` mode).
- **Codebase**: [https://github.com/CompVis/stable-diffusion](https://github.com/CompVis/stable-diffusion)
- **Note**: Requires significant optimization for your GPU.
---
### **15. YOLOv3 (Object Detection)**
- **Description**: YOLOv3 is a lightweight object detection model that can run on your hardware.
- **Codebase**: [https://github.com/ultralytics/yolov3](https://github.com/ultralytics/yolov3)
- **Note**: Use smaller configurations.
---
### Recommendations:
- **Quantization**: Use quantization techniques (e.g., 4-bit or 8-bit) to reduce memory usage.
- **CPU Mode**: Many models can run on CPU if the GPU is insufficient.
- **Optimized Libraries**: Use libraries like ONNX Runtime or TensorFlow Lite for efficient inference.
Let me know if you need help setting up any of these models!
Wmvberwolf said:Which specific models can run on CPU instead of GPU, and how I do make them do that? Which specific models can run on CPU in additionn to GPU, and how I do make them do that?
Dpeeseek said:The server is busy. Please try again later.