Skip to main content

Running LLMs locally using LM Studio

As I like to experiment a lot with AI, I always have to be careful and keep my token usage under control. And although the token cost has decreased over time for most models, the expenses can go up quite fast.

That is one of the reasons I like to use  (Large) Language Models locally.  There are multiple ways to run a model locally but my preferred way so far was Ollama (together with OpenWebUI). I also experimented with Podman AI Lab but I always returned to Ollama in the end. 

Recently a colleague introduced me to LM Studio, another tool to run and test LLM’s locally. With LM Studio, you can:

  • Run LLMs offline on your local machine
  • Download and run models from Hugging Face
  • Integrate your own application with a local model using the LM Studio SDK or through the OpenAI endpoints
  • Use the built-in RAG support to chat with your local documents

More than enough reasons to give it a try…

Getting started

  • I downloaded the installer from the website and followed the installation wizard. Once the installation has completed click on Finish:

 

  • If you selected the Run LM Studio checkbox, LM Studio will be started immediately and you will be welcomed by an onboarding wizard:

 

  • Click on the Get your first LLM button. The next onboarding step appears where it suggests me to download a first model(in this case DeepSeek R1).
    • Notice the Enable local LLM service on login option. By checking this option, you can use the LM Studio local LLM server without having the LM Studio application open.

 

  • Click on Download to download the suggested model.

 

  • Once the download has completed, a Start New Chat button appears. Click on it to continue.

  • We finally get the LM Studio UI in front of us. Let us first load the downloaded model by clicking on the Load Model button in the notification popup.

  • Once the model is loaded, we can start asking questions by typing a message in the chat window and hitting Send.
 

Exploring some features

Now that we have the basics runnng, let’s explore some of the nice features that LM Studio has to offer.

If you click on the settings icon in the top right corner, you get a lot of options to easily tweak the used model. 

For example you can easily enable structured output(if the model supports it):

 

Another feature I like is that you can switch between ‘User’ and ‘Assistant’ mode in the chat. This is useful for few-shot prompting and other scenario’s:

I already mentioned the RAG integration:

Don’t forget to check out the Developer tab as well where you can run the LLM server and expose OpenAI compatible endpoints to your applications:

 

It’s too soon to tell if I will use this instead of Ollama but it is certainly worth to give it a try.

More information

Tokenizer - OpenAI API

Run LLMs locally using Podman AI Lab

Running large language models locally using Ollama

Explore and test local modals using Ollama and OpenWebUI

LM Studio - Discover, download, and run local LLMs

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more