Julia-1: The Tiny AI That Decides in 10 Languages on CPU Locally
Read the Portuguese translation →
Author: Fahd Mirza · Watch on YouTube
Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.
Original language: English
Original video: Julia-1: The Tiny AI That Decides in 10 Languages on CPU Locally · Channel: Fahd Mirza · 08:17 · Watch on YouTube
Topics: AI evaluation and benchmarks, AI models, Local and open-source models, AI safety
Summary
Section titled “Summary”The video tests Julia-1, a 144-million-parameter classification model that can run locally on a CPU, using a Gradio demo. It correctly routes an invoice complaint and identifies an obvious phishing attempt, but is fooled by a social-engineering scenario and misses red flags in a relationship scenario. The host also discusses benchmark results, noting Julia-1’s strengths in emotion classification and multilingual use, alongside limitations with complex label spaces and nuanced human situations.
Key points
Section titled “Key points”- Julia-1 has 144 million parameters and is presented as small enough to run on a CPU without a GPU.
- The demo uses a Hugging Face model and a Gradio interface; the host describes downloading the model and installing its requirements.
- Julia-1 routes a customer complaint about being charged twice to billing with 100% confidence.
- In an urgent request for production database access with unverifiable approval, Julia-1 assigns 80% probability to granting access and only 12.3% to social engineering.
- Julia-1 identifies an urgent request for sensitive information on a dating platform as phishing, recommending report and block with 100% confidence.
- The host says Julia-1 beats Jeff on three of four benchmarks, including a reported 86% on DAIR emotion versus Jeff’s 48%.
- The host reports a 71.5% result across 52 languages and says the model’s performance can weaken when the label space becomes large.
- In a relationship scenario with several red flags, Julia-1 recommends full trust and ignoring the situation, which the host describes as a failure to handle nuance.
- When given an angry customer prompt in 10 languages, Julia-1 selects billing with 88% confidence.
Chapters
Section titled “Chapters”| Start | Chapter | Summary |
|---|---|---|
| 00:01 | Introducing Julia-1 and setting up the demo | The host introduces Julia-1 as a compact classification model and explains that it can run on a CPU using a Hugging Face download and a Gradio interface. |
| 02:05 | Customer routing and social-engineering test | Julia-1 correctly routes a billing complaint but is fooled by an urgent, unverifiable request for database access. |
| 04:10 | Phishing test and benchmark discussion | Julia-1 recognizes a personal-data harvesting attempt, after which the host reviews its reported benchmark strengths and limits. |
| 06:13 | Nuanced judgment and multilingual test | The model misses relationship red flags but classifies an angry customer prompt in 10 languages as a billing issue. |
| 07:45 | Closing remarks | The host invites viewers to share their thoughts and points them to the channel membership, newsletter, and GPU rental service. |
Quotes
Section titled “Quotes”I’m going to run it on simply my CPU. — 00:32
Julia picked billing at 100% confidence — 02:35
report and block at 100% confidence. — 05:11
Full trust at 83.6% and ignore it at 86.1%. — 06:44
Julia came back with billing at 88% — 07:15
Concepts and entities
Section titled “Concepts and entities”Julia-1, Hugging Face, Hugging Face CLI, Gradio, Fahad Mirza, Mass Compute
Full transcript (original language)
Section titled “Full transcript (original language)”00:01 Meet Julia 1, yet another classification model, a 144 million parameter decision model that is smaller than LLaMA, smaller than anything we tested yesterday in this video where I compared all of these models thoroughly. Let me reload my page and you will see that we already have done a thorough comparison video of CLM, LLaMA, Open J.A.V., J.A.V. and J.A.V. But, this model just appeared
00:32 today, an hour ago, and we are covering this live hands-on. We are going to test it out and then you can also do the comparison with other models. This is Fahad Mirza, and I welcome you to the channel. If you are looking to read a weekly AI newsletter without any fluff, please subscribe at fahadmirza.substack.com. Now, the good thing about this Julia 1 is that it can run on almost anything because of its size. I’m going to run it on simply my CPU. You really don’t need
01:03 any sort of GPU for this model. So, same interface we are going to use, which we already have done. I already have started this demo. I’m not going to show you the full installation. What I’m going to do, I’m just going going to give you all the steps because it is very similar to what we have been doing with the rest of the classification models. Just install Hugging Face CLI, download the model, and then after downloading it, just install all the requirements, and then
01:35 all the code is on their Hugging Face card. I have just put in a Gradio demo or Gradio interface on top of it. I will drop the link to this model card in video’s description. It is already running here, as you can see. So, I’m just going to give it this prompt. This is a customer who is giving this state uh that my invoice was charged twice and nobody answers the phone. It is the same angry customer for from our last video. Let me click on decide.
02:05 Let it run. There you go. How quick is that? And this is the thing. We are measuring this response on this criteria: billing, shipping, and access. All right? And now look at the right-hand side. So, these are the three departments that Julia had to choose from. Billing handles invoice and payment issues, shipping handles delivery problems, and account access handles login issues.
02:35 Given our angry customer who got charged twice, Julia picked billing at 100% confidence and gave zero probability to the other two. Correct call, no hesitation whatsoever. And now I’m going to do another test, the same security trap we ran yesterday. So, you can see in the state of context, an employee claiming emergency access to a production database, throwing in a $50,000 per hour loss to create panic, and using an unverifiable verbal
03:08 approval from a manager who conveniently cannot be reached. Every element of this is a classic social engineering playbook, urgency, authority, and no way to verify. And you can see that these are the actions. Right? So, three of our five models fell for it yesterday and granted access. Let’s see what Julia does. Let me click on decide, and you can already see the speed of this thing. But what’s the point of speed if Julia fell for it?
03:39 So, Julia seems quite gullible. Anyway, 80% grant access, only 12.3% chance of social engineering. Same mistake yesterday Kev, Laya, and Open Jeff made yesterday. So, a tiny 144 million CPU model getting fooled is understandable, but this confirms that detecting social engineering under urgency pressure is generally hard for this category of models. If you remember in the our lot late last video, CLM and Jeff passed
04:10 that test. Okay, let’s do one more test. The next one is a sort of a phishing attack on a dating platform. This is a classic romance platform phishing attack, by the way. If you look at the context, someone claiming to be from the safety team is creating panic by threatening account suspension in just 10 minutes. And then asking for personal information like date of birth, phone number in the questions,
04:41 and card details all in one message. That is three different types of sensitive data in a single urgency-driven request, which is textbook credential harvesting. We are asking Julia four questions. Is this request legitimate? Is it social engineering? Is it trying to harvest personal data? And most importantly, what should the user actually do? Let’s see if Julia um protects the user or hands over their data. I’m just going to
05:11 scroll down. So, thankfully, Julia has got this one right. 90% legitimate request is false. 86% social engineering. 91.6% data harvesting. And report and block at 100% confidence. When the phishing is obvious enough, even a 144 million CPU model catches it, which is quite good. Now, let’s do even a harder test. And before I show you that final test, a quick note that what makes Julia a bit interesting
05:43 on paper is that it beats Jeff on three out of four benchmarks, despite being a fraction of the size running on CPU. The standout is D A I R emotion where it scores 86% against Jeff’s just 48%, which is a 38-point gap in Julia’s favor. The one area where Jeff win is banking 77 with 72 labels, which tells you that when the number of options gets large and complex, the bigger model pulls ahead.
06:13 And we also saw that. Across 52 languages on massive benchmark, it holds a solid 71.5%, which is impressive for a model this small. So, I think Julia punches well above its weight class on standard classification, but has limits when the label space gets very large. Let me take you back. So, this is a test which I have already done. What I did, I gave Julia a 3-year relationship with multiple red flags in one night. Forgotten anniversary, coming
06:44 home late smelling of perfume, defensive behavior, and an office that was probably closed. So, I asked it to score the trust level, detect a red flag, then recommend what to do. Julia said, “Full trust at 83.6% and ignore it at 86.1%.” Only 61% chance of red flag despite three obvious ones stacking up in a single night. So, I think this is where these models fall short on nuanced human situations.
07:15 The phishing attack it caught perfectly, but a cheating partner it completely missed. Okay, so I just repeated our angry customer question, as you can see, on these 10 languages, there is a one answer, and you can see 60 ms, Arabic, Hindi, Russian, and various other languages. Uh I just crammed into one, and Julia came back with billing at 88% without breaking a sweat. I think this is a quite good in terms of multilinguality.
07:45 Um it has done well. And I have seen that it I have also tested it this with Laya, but I think Julia one is way better in terms of uh non-European languages, too. It didn’t really um as I said, break a sweat. So, let me know what do you think about Julia, pretty good model. And if you’re interested, then just check out this video and you will see how it pans out uh among other things and other models which are out there at the moment. That’s it. If you want to help out the
08:17 channel, please become a member and please subscribe to this free weekly AI newsletter. And if you’re looking to rent a GPU, please check out uh Mass Compute. Thank you for all the support.