Alright, my buddies, I’m again with one other submit primarily based on my learnings and exploration of AI and the way it’ll match into our work as community engineers. In at present’s submit, I wish to share the primary (of what is going to seemingly be many) “nerd knobs” that I believe all of us ought to pay attention to and the way they are going to influence our use of AI and AI instruments. I can already sense the joy within the room. In spite of everything, there’s not a lot a community engineer likes greater than tweaking a nerd knob within the community to fine-tune efficiency. And that’s precisely what we’ll be doing right here. High quality-tuning our AI instruments to assist us be simpler.
First up, the requisite disclaimer or two.
- There are SO MANY nerd knobs in AI. (Shocker, I do know.) So, should you all like this type of weblog submit, I’d be completely satisfied to return in different posts the place we have a look at different “knobs” and settings in AI and the way they work. Nicely, I’d be completely satisfied to return as soon as I perceive them, at the least. 🙂
- Altering any of the settings in your AI instruments can have dramatic results on outcomes. This contains growing the useful resource consumption of the AI mannequin, in addition to growing hallucinations and lowering the accuracy of the data that comes again out of your prompts. Take into account yourselves warned. As with all issues AI, go forth and discover and experiment. However accomplish that in a protected, lab surroundings.
For at present’s experiment, I’m as soon as once more utilizing LMStudio working regionally on my laptop computer quite than a public or cloud-hosted AI mannequin. For extra particulars on why I like LMStudio, try my final weblog, Making a NetAI Playground for Agentic AI Experimentation.
Sufficient of the setup, let’s get into it!
The influence of working reminiscence measurement, a.okay.a. “context”
Let me set a scene for you.
You’re in the course of troubleshooting a community challenge. Somebody reported, or seen, instability at a degree in your community, and also you’ve been assigned the joyful activity of attending to the underside of it. You captured some logs and related debug info, and the time has come to undergo all of it to determine what it means. However you’ve additionally been utilizing AI instruments to be extra productive, 10x your work, impress your boss, you understand all of the issues which might be happening proper now.
So, you resolve to see if AI may help you’re employed by means of the info sooner and get to the basis of the problem.
You fireplace up your native AI assistant. (Sure, native—as a result of who is aware of what’s within the debug messages? Greatest to maintain all of it protected in your laptop computer.)
You inform it what you’re as much as, and paste within the log messages.
After getting 120 or so strains of logs into the chat, you hit enter, kick up your ft, attain in your Arnold Palmer for a refreshing drink, and look forward to the AI magic to occur. However earlier than you possibly can take a sip of that iced tea and lemonade goodness, you see this has instantly popped up on the display:
Oh my.
“The AI has nothing to say.”!?! How might that be?
Did you discover a query so troublesome that AI can’t deal with it?
No, that’s not the issue. Take a look at the useful error message that LMStudio has kicked again:
“Making an attempt to maintain the primary 4994 tokens when context the overflows. Nevertheless, the mannequin is loaded with context size of solely 4096 tokens, which isn’t sufficient. Attempt to load the mannequin with a bigger context size, or present shorter enter.”
And we’ve gotten to the basis of this completely scripted storyline and demonstration. Each AI instrument on the market has a restrict to how a lot “working reminiscence” it has. The technical time period for this working reminiscence is “context size.” Should you attempt to ship extra information to an AI instrument than can match into the context size, you’ll hit this error, or one thing prefer it.
The error message signifies that the mannequin was “loaded with context size of solely 4096 tokens.” What’s a “token,” you surprise? Answering that may very well be a subject of a completely completely different weblog submit, however for now, simply know that “tokens” are the unit of measurement for the context size. And the very first thing that’s completed while you ship a immediate to an AI instrument is that the immediate is transformed into “tokens”.
So what can we do? Nicely, the message provides us two attainable choices: we will improve the context size of the mannequin, or we will present shorter enter. Generally it isn’t a giant deal to offer shorter enter. However different occasions, like once we are coping with giant log information, that choice isn’t sensible—the entire information is necessary.
Time to show the knob!
It’s that first choice, to load the mannequin with a bigger context size, that’s our nerd knob. Let’s flip it.
From inside LMStudio, head over to “My Fashions” and click on to open up the configuration settings interface for the mannequin.
You’ll get an opportunity to view all of the knobs that AI fashions have. And as I discussed, there are a whole lot of them.
However the one we care about proper now’s the Context Size. We will see that the default size for this mannequin is 4096 tokens. However it helps as much as 8192 tokens. Let’s max it out!
LMStudio gives a useful warning and possible motive for why the mannequin doesn’t default to the max. The context size takes reminiscence and assets. And elevating it to “a excessive worth” can influence efficiency and utilization. So if this mannequin had a max size of 40,960 tokens (the Qwen3 mannequin I take advantage of typically has that top of a max), you won’t wish to simply max it out straight away. As a substitute, improve it by just a little at a time to seek out the candy spot: a context size sufficiently big for the job, however not outsized.
As community engineers, we’re used to fine-tuning knobs for timers, body sizes, and so many different issues. That is proper up our alley!
When you’ve up to date your context size, you’ll have to “Eject” and “Reload” the mannequin for the setting to take impact. However as soon as that’s completed, it’s time to benefit from the change we’ve made!
And have a look at that, with the bigger context window, the AI assistant was in a position to undergo the logs and provides us a pleasant write-up about what they present.
I significantly just like the shade it threw my manner: “…contemplate in search of help from … a certified community engineer.” Nicely performed, AI. Nicely performed.
However bruised ego apart, we will proceed the AI assisted troubleshooting with one thing like this.
And we’re off to the races. We’ve been in a position to leverage our AI assistant to:
- Course of a major quantity of log and debug information to establish attainable points
- Develop a timeline of the issue (that can be tremendous helpful within the assist desk ticket and root trigger evaluation paperwork)
- Determine some subsequent steps we will do in our troubleshooting efforts.
All tales should finish…
And so you might have it, our first AI Nerd Knob—Context Size. Let’s overview what we realized:
- AI fashions have a “working reminiscence” that’s known as “context size.”
- Context Size is measured in “tokens.”
- Oftentimes occasions an AI mannequin will assist a better context size than the default setting.
- Rising the context size would require extra assets, so make modifications slowly, don’t simply max it out utterly.
Now, relying on what AI instrument you’re utilizing, you might NOT be capable of alter the context size. Should you’re utilizing a public AI like ChatGPT, Gemini, or Claude, the context size will depend upon the subscription and fashions you might have entry to. Nevertheless, there most undoubtedly IS a context size that can issue into how a lot “working reminiscence” the AI instrument has. And being conscious of that truth, and its influence on how you need to use AI, is necessary. Even when the knob in query is behind a lock and key. 🙂
Should you loved this look beneath the hood of AI and wish to find out about extra choices, please let me know within the feedback: Do you might have a favourite “knob” you want to show? Share it with all of us. Till subsequent time!
PS… Should you’d prefer to study extra about utilizing LMStudio, my buddy Jason Belk put a free tutorial collectively known as Run Your Personal LLM Regionally For Free and with Ease that may get you began in a short time. Test it out!
Join Cisco U. | Be part of the Cisco Studying Community at present totally free.
Study with Cisco
X | Threads | Fb | LinkedIn | Instagram | YouTube
Use #CiscoU and #CiscoCert to affix the dialog.
Learn subsequent:
Share: