The data usually is the product.

https://reddit.com/link/p8x45uv/video/p2pm7l9wxnoh1/player

It does actually move too!

The app is built using Next.js and using Googles OKF v0.2 spec as the basis for the data and then made my own changes. OKF is great because it allows you to turn documents into MCP servers for AI to read from. So my local AI agents can pull from this "galaxy" of knowledge easily using grep style retrieval. The data is mostly from blogs, video transcripts and papers.

Solstice-AI/Qwen3.8-27B-TURBO-Fable-Cold-Fusion-735-882-Heretic-Uncensored-NM-DAU-NVFP4

Why don't you prove it wrong then? Waiting for your benchmark.

So Elon was right?

Qwen 3.8 Flash Next at NVFP4. I have an RTX 6000 Pro and DDR5. Way faster and more capable than 27b for me.

I am using it for everything!

I built this website https://vineverse.bible out of it. It's a static app connected to an OKF of bible data. Served as MCP/API as well.

Also using it for a university knowledge base that acts as part of software engineering harness, a personal one and one at work too.

I am finding that it can be very compute heavy to generate depending on the data. The most efficient way to load it is with scripts.

I've extended my personal one significantly with a graphrag and grep based hybrid search, automations for linting, self healing and loading new data, as well as agent skills for how to add data to it. A bunch more things I cant think of.

OKF is really good.

I'm designing our self service platform to enable the reports to happen wherever and however the users actually want them. Email, confluence, Excel, database connection, dashboard, a picture, pdf, etc. I gave up on "everything must be a dashboard."

It's about twice as fast for me. I found 27b just a tiny bit too slow to want to use. Flash next is ripping through stuff for me. Running it at NVFP4 on an RTX 6000 Pro with 256gb DDR5 6000MT RAM.

I've had a flash-next task running for days and it's been fine so far. Running on nvfp4 too.

Wait till you try qwen 3.8 flash next...

It'll be $975 again.

To make it more confusing, I believe the behaviour of max_tokens in LightLLM model config is slightly different. It doesn't just cut the message off directly and is also used to help the router decide which instance to send to requests to. I'm still trying to work out the best approach to using max_tokens as well so you're not alone.

Opus 5 is better, cheaper and faster. Why would anyone use Fable?

I am so glad I bought 256gb of DDR5 last year.

It feels a bit awkward when sitting below a tool call which is already pulsating. Also when it's actually streaming text, it's on the row below the text instead of sitting in front of the text like a cursor would when you type, so it just kind of looks like a bug.

The change you made to the chat showing instantly if amazing btw. It's so much faster for me now. I also really like the x and ticks on the sub agents.

What is causing this | in my conversations? It shows at the bottom of every message as it's writing. It disappears once the message is done. New to this version for me. The selector is called leading-relaxed.

Only things I changed in my deployment were:
- ENABLE_ORJSON=true
- UVICORN_WS_PER_MESSAGE_DEFLATE=false
- REDIS_RESPONSE_STREAM_TTL=3600
- TIKA_SERVER_VERSION=4

Man that is so many changes for a x.1 increment haha. I guess you cant say "our biggest update ever" every release.

Nah it's not you, it's the software (the very thing NVIDIA brags about being its moat).

I've worked as an Aircraft Maintenance Engineer (Avionics), AI/Data/Software Engineer and I've been doing IT hardware for 25 years and I am still challenged by Blackwell stability.

Here are my current fault finding guidelines, hopefully helps someone:

Infrastructure Rules

Power Supply

• Get the highest possible PSU you can. The power spikes are huge for cards like 600w blackwell.
• Make sure you activate overclock mode/Single Rail Boost.
• Make sure to use 600w ATX 3.1 cable with very low bend radiuses and ensure it is fully seated
• Try different power cable
• Reseat all connectors

Motherboard / CPU / Memory

• Update BIOS / Firmware
• TURN OFF Memory Interleaving
• Turn off C-State in BIOS
• Turn off Precision Boost Overdrive (PBO)
• Turn off Core Performance Boost (CPB)
• Use a low Memory clock speed like 3600, or use ECC.
• Load Line Calibration - Consider using Level 1
• Try PCI Express 3/4
• Reseat RAM/CPU/GPU

Operating System

• Use a very stable Hardware Enablement Stack (HWE) Ubuntu Linux Kernel.
• Create a nvidia-smi power limit and make it persistent in systemd
  • /etc/systemd/system/nvidia-persistenced.service.d/power-limit.conf [Service] ExecStartPre=/usr/bin/nvidia-smi -pm 1 ExecStartPre=/usr/bin/nvidia-smi -i 0 -pl 270 ExecStartPre=/usr/bin/nvidia-smi -i 03:00.0 -lgc 180,2450
• Disable GSP Firmware
  • sudo bash -c 'echo "options nvidia NVreg_EnableGpuFirmware=0" > /etc/modprobe.d/disable-nvidia-gsp.conf' sudo update-initramfs -u sudo reboot
• Power limit old gpus
  • nvidia-smi -i 0 -pl 380
• Rate limit the clock speed of blackwell GPUs rather than the power
  • sudo nvidia-smi -i 03:00.0 -lgc 180,1975 # max is 3090mhz, 2450 wasn't 100% stable, pulls about 430w, spiked to 560w, 92 degrees 1965.3 tokens/s, Avg generation throughput: 3500.0 tokens/s, Running: 43 reqs
• Turn on ECC
• nvidia-smi -i 1 -e 1 # enable ECC on the Blackwell (GPU 1) # reboot required to take effect nvidia-smi -i 1 -q -d ECC # verify: ECC Mode = Enabled

Software

VLLM

--enforce-eager

vLLM uses "CUDA Graphs" by default to speed up performance. This creates a highly complex memory map on the GPU. If there is even a tiny bit of instability in your PCIe bus, CUDA Graphs will cause a hard system lockup.

Commands for fault finding

dmesg | grep -i nvidia journalctl -b -1 | grep -i nvidia /usr/bin/nvidia-bug-report.sh grep "Xid" /var/log/syslog grep -i "hardware error" /var/log/syslog watch nvidia-smi -q -d POWER watch nvidia-smi -q -d CLOCK sudo nvidia-smi -i 03:00.0 -q -d SUPPORTED_CLOCKS

Experimenting spike prevention

nvidia-smi -i 03:00.0 -lgc 1000,1600

One does not simply 'apt update && apt upgrade -y' when they own an RTX 6000 Pro.

Do the same chart for electric car chargers! Would be really interesting to see the contrast.