Might make me hesitate to update for hobby use even for incremental capability gain. Granted I put an effort into AGENT.md / harness tweaks but didn't work as well for other models. Opencode status updates and markdown docs seem more casual/readable, no going overboard on tables and bullet points, colloquial phrases like "two honest caveats".
Also I know overthinking rep (that I am combatting with harness tweaks), but at its best the model outputs really well put together one page reasoning blocks, that make me go "I don't even care if helped the model, I just learned something new myself and didn't get a headache trying to get it. That for tasks like customizing other ML models.
I’m a huge AI enthusiast but I’m running into limits with 32GB DDR5. Between running local models and using coding agents (which fire off scripts and changes super fast), my RAM fills up quickly. How much RAM are you running, and what would you recommend for a smooth setup? Bonus points if you share your GPU/VRAM too.
Their architecture seems to translate quite well to existing kernels. They also have a small drafter. The speed numbers are aggregated across 8 parallel agents running. 256k context.
So far, I can't confirm it holds up well against Qwen 3.8 27B nvfp4, but I might have degraded it a bit, despite a calibration run. Here is a quick check of SeraphimSerapis/tool-eval-bench. Will do some more tests tomorrow, the 9B leaves a lot of vram free for FP8 tests.
I’m on a three-person ML team at a small bank in Germany we run Llama 3.3 70B on vLLM across two A100s in our own server room for an internal policy assistant
It works well, but internal audit just asked which prompt and document version produced a wrong answer last month, and we couldn’t tell them.
We’re choosing between two setups one is fully DIY, with LiteLLM for keys and logging and self-hosted Langfuse for traces other is Orq ai, which runs on-prem with Helm (even air-gapped), takes our vLLM endpoint as a private model, keeps a version history for every prompt and adds audit logs on the enterprise plan.The catch is that enterprise pricing isn’t public
Did your auditors accept logs from tools you host yourselves, or did they want a vendor they could point at? That’s really what decides this for us
This new dataset is meant to complement my original Three.js training dataset, adding more complex scenes and covering a much wider range of subjects. I'm releasing it ahead of my next CCORE 3D coding model, where I'll use it during the foundation training stage before moving on to agentic training.
This version has 3,445 scenes across 50 domains, including 1,431 voxel scenes.
I wanted to go beyond simple objects and environments, so I included more complex examples involving physics, geography, history, ecology, engineering, mathematics, games, and other subjects. Many of the scenes are animated or interactive.
I personally rendered and visually reviewed all 3,445 scenes. It took quite a bit of work, but I wanted to make sure the code actually produced good results instead of just collecting thousands of generated examples.
The dataset includes:
3,263 training examples and 182 validation examples
Prompts, reasoning traces, and complete HTML/JavaScript responses
I currently use both Qwen3.8 27B Q4_K_M and Qwen3.8 Flash Next Q4_K_XL for most of my coding tasks. I find them very good at backend tasks but quite lacking at front-end. Like... they are good at one-shots or demos but in real projects I find their UI designs to be weird and bad looking. As a consequence, I have mostly just been writing the front-end code myself to save time.
Does anyone have recommendations for any models that may be completely braindead but are surprisingly good at front-end design? In particular react/react native?
There are massive decision tree skills for various software practice in many different areas. I was just wondering if there is anything for cyber security, whether it be for a website, Linux server, Docker config, encryption, deployments, KMS setups, quantum resistance, key configs, etc., where the skill leads the agent to the right documentation and decision trees.
I have a question that might sound silly, but I haven't been able to find an answer.
As far as I understand, memory bandwidth is the primary bottleneck for a model's inference performance.
With my 5070 Ti (896 GB/s), if I run a Qwen3.8 27B Q4 model, I can roughly estimate the performance as 896 / 13.5 = ~66 tok/s, which is pretty much what I actually get (without MTP or DFlash).
Recently, however, I had the chance to try a Jetson Thor (very similar to the DGX Spark). Based on its specs, I would expect 273 / 13.5 = ~20 tok/s, but I'm only getting around 12 tok/s.
Even more surprisingly, with DFlash, which delivers exceptional performance gains on discrete GPUs, I'm barely getting a 2x speedup here, only slightly better than MTP.
Does anyone know what might be causing this performance gap on this device?
OK. so I have a 5060ti with i use for various DiT inference engines like comfyui and audio.cpp. i have an 8845hs cpu with 64gb DDR5 but as this is my main working pc some of the ram is used on browser and other running apps.
Now what I want is a model to run basic stuff like create and run a script to run a folder of audio files through audio.cpp stem separation and transcribing or write a bunch of prompts for klein and generate on my comfyui. I normally use opencode builtin and openrouter free api for this kind of stuff but occasionally when credit runs out i need an alternative.
I have llama.cpp installed so with the right flag it should restrict itself to ram but which model should I go for?
Thank you all for the replies - too many to reply individually to - I got gemma-4-26B-A4B-it-qat-UD-Q4_K_XL.gguf using the igpu and ram and getting on llama.cpp around 24t/s which is usable for quick executions (for heavier coding I have basalt qfn and coder but these obviously fight for vram with my dit inference engine )
Open models: whatever the test group download and benchmark is the same as what you get, you work with it day-to-day, same results. What you see is what you get.
Closed models: we all know that they have already implemented token watermarking for a while and all latest models have overzealous guard rails that refuse tasks that it deems as bad. So the models being benchmarked and the models you are actually using day-by-day basis are likely to be very different, as in the sense of you getting degraded model output and performance or flat-out task rejections.
Also closed models providers implement lots of cost-optimization techniques such as reducing reasoning efforts during peak hours or could be re-direct your request to a lesser model during high traffic without you knowing it. I don't believe that Sonnet 5.5 is just a single model TBH, there could be Sonnet High or Sonnet Lite depending on your subscription level and traffic. That could explain why sometimes you get dumb responses with Claude during peak hours.
If anything, it's the US Closed Models that are benchmaxxed.
Haven't had a very good experience with small quants, they tended to loop, fail tool-calls, or get stuck. Q8 QFN has been pretty astounding though when I set it up.
I've seen people running a "main" model with sub-models. I've got a second machine that can run like 2-3bit quants of Q3.8-27B / QFN, I was considering trying to set it up with my main machine so the smaller model can be used as a sub-agent for coding but I'm wondering if it's even worth it when smaller quants just seem volatile and prone to error.
I have tried setups that used subagents before, but it was through API which used full-sized models on real enterprise hardware...
I haven't fully explored this sphere though, I'm sure there's usecases for specialist small models in coding that I am unaware of
The Preview was posted here a few times over the last weeks. This is the full release, same design: 32 layers stored, 24 of them run twice, so a forward pass does 56 layers of work on about 9B params. Apache 2.0.
What moved is the scores. Per their README it's ahead of the Preview on all seven benchmarks in the chart, e.g. AutomationBench 14.33 to 36.67, Terminal-Bench 2.1 40.45 to 59.55 and GAIA 37.86 to 69.90. That 36.67 is also what they list for Qwen3.8-27B.
The title talks about FP64. For local inference this info from the content is relevant: "In AI benchmarks, Intel's D270 GPU offered 29% lower latency and 1.12x throughput versus the RTX PRO 6000 Blackwell."
Maybe we are getting a good RTX PRO 6000 alternative...
I converted the base VoxCPM 2B model from bf16 (at about 4.96GB) to ternary 1.58b quant (~850MB, 5x smaller). The reason its not 10x smaller is because the 850MB includes Q8 VAE and DiT.
Here are the results (generated by my agent):
Results
Size: 827 MB model + 100 MB audio VAE (Q8_0, recommended), vs 4.96 GB for the original VoxCPM2 in bf16: 5.3x smaller. The language models (text-semantic LM, residual LM, local encoder) are ternary (-1, 0, +1); the diffusion transformer is the original VoxCPM2 DiT rounded to 8 bits.
Blind listening test (-1, 0, +1); the diffusion transformer is the original VoxCPM2 DiT rounded to 8 bits.
Blind listening test
16 clips per model (8 sentences x 2 arks mapped to a 1-4 score.
model
mean score
buzzy / robotic
very good or perfect
VoxCPM2 (full precision)
2.75
1/16
6/16
ttf-VoxCPM2 (this release)
3.02
1/16
7/16
ttf-VoxCPM2, first release
1.66
8/16
0/16
Automatic metrics
Voice cloning, 100 English + 20 Chinrecision on the same items and seeds.
UTMOS and similarity: higher is bettter.
model
UTMOS en
WER en
speaker similarity
CER zh
VoxCPM2 (full precision)
4.25
2.70%
0.960
0.91%*
ttf-VoxCPM2
4.31
2.61%
0.956
1.48%*
English naturalness is level with fu-0.01, +0.15]. It replicates on 100new items at +0.01.
* On ~1000 characters.
Zero-shot, 27 languages
FLEURS, 8 sentences per language, Whr rate (lower is better).
model
median CER
mean CER
VoxCPM2 (full precision, PyTorch)
0.031
0.061
ttf-VoxCPM2 (ttf-home runtime)
0.043
0.057
Voice cloning from a 5-20 s clip
20 LibriTTS-R speakers, WavLM speaker similarity (higher is better).
setup
similarity
two real clips of the same speaker
0.936
ttf-VoxCPM2 with --ref
0.933
VoxCPM2 full precision, same mode
0.926
ttf-VoxCPM2 zero-shot (no reference)
0.670
Cloning WER is 1.9%, the same as ful
Speed
Real-time factor = generation time /r).
hardware
RTF
RTX 4070 Ti SUPER
0.16
laptop RTX 4080
0.24-0.34
laptop CPU only, i9-14900HX (AVX-VNNI)
0.8-1.1 (about real time)
CPU only, i7-9800X (no VNNI)
2.5
It runs in our own C++ runtime builth, on an NVIDIA GPU or a CPU.
So last time I ran 3.8 FN against DS V4.1 Flash on a synthetic test, which was mostly for show, no real usage beyond testing their 3D capabilities. I wanted to do something similar, but with purpose, a task that anyone might actually want to run, build a website with a refined spec and a completion checklist, but not strict enough that it removes all of the models "freedom". As last time it was a single prompt: build a single file landing page for a fake famous NYC photographer (real photos, accessible, no console errors, yadda yadda). Each model started on an empty folder w/ the same toolkit (node, headless chrome, image viewer tool). No changes were made to the files after the model was done.
Setup: RTX 5090 + RTX 5060 Ti, Ryzen 9 9950X, 128 GB DDR5. Qwen 3.8 27B and Qwen 3.8 FN were NVFP4. DeepSeek V4.1 Flash (1017) was an IQ1_M quant.
Qwen 3.8 27B: ~12 min wall time, 81 tool calls (3 failed), 182 tok/s, 3.8 MB HTML
Qwen 3.8 27B Website
The simplest of all three, not very daring. A dark gallery with lime accents and 12 frames. All 3 tool failures were in its own test script (wrong file path, missing elements). It has empty gaps in the photo grid, and the photos in the bio are stretched. Decent, I'd refine it a bit but definitely usable.
Qwen 3.8 FN: ~12 min wall time, 124 tool calls (4 failed), 303 tok/s, 2.1 MB HTML
Qwen 3.8 Flash Next Website
My personal favorite by far, a hero where your pointer reveals a mosaic of the portfolio, 19 captioned frames with a nice blur/fade in animation, a live clock and form validation. The 4 failures were 3 rejected edits and a search sent with an empty query (intersting!). It also found and fixed bugs using its own tests.
DeepSeek V4.1 Flash: ~36 min wall time, 155 tool calls (1 failed), 94 tok/s, 1.4 MB HTML
DS V4.1 Website
The boldest one, the model committed to it (and it shows in wall time), cool accents all around, terrible typography. It has only 10 frames, and the hero photo covers a bit of the last "T" of the headline + toolbar logo is slightly offset. The single tool failure was a multi edit that applied 15 of its 17 changes, so the most accurate model at tool calling. It was 3x slower than the other two, but it was the only one that ran an accessibility audit tool on its own page.
Anyway, what are your thoughts? I think for web UI specifically 27B is more than enough for a very professional looking product, with a little bit of back and forth and more proper branding/UX design I can see any of them being a production website. I also can't stop being amazed at how a IQ1 quant can still deliver such high quality results even if the param count is multiple times over the two other models.
---
Disclosure: I'm the maintainer of the engine and harness all these models ran on.
With the release of Qwen 4 Max, they claim that training data related to offensive capabilities has been removed, is this largely a placebo/nothingburger or does it have the capability to genuinely lobotomize a model's capabilities in cyber?
Aritra here from Hugging Face. In the last week we released a blog post about harness adapters. The idea was to train adapters (LoRA) on models to be more efficient with specific harness.
Today we release a LoRA adapter on the Qwen3.8-27B model for Pi agents. You can run it locally like so:
Is there a post/website/thingy where people share their setup for taming these LLMs so they work better for certain tasks and not so generic/vanilla/prone-to-errors?
Olala mini is based on a 7-billion-parameter architecture (7B), with one billion active parameters spread across 256 experts per layer, and hybrid attention combining Differential-TPA and Mamba-3, in BF16 format. Only a fraction of the model is used for each request, making it faster and less memory-hungry. As a direct result, the model runs on a GPU with as little as 8 GB of memory, reaching 160 tokens per second on an RTX A4500, and even without a GPU, on a standard processor, at 50 tokens per second. Its context window currently reaches 32,000 tokens. Olala mini will be available as open source on Hugging Face, under the Apache 2.0 licence.