GPT 5.5 vs DeepSeek V4 Pro

Shares his thoughts on ai

DeepSeek V4 pro effectively reverse-engineered a recently released 100B LLM architecture entirely on its own and then adapted llama.cpp to run it. (in \~10M token and less then $2 )

The best thing I read in the last hours was a user who said "We werent the real customers, only the beta testers". This, or local LLMs Will be the next aproach for Freelancers who don't want or cant spend thousands on tokens usage.

Tested DeepSeek V4 Pro on FoodTruck Bench — our 30-day agentic benchmark where models run a food truck via 34 tools (locations, pricing, inventory, staff, weather, events) with persistent memory and daily reflection.

First Chinese model to land in the frontier tier on our benchmark. Tied with Grok 4.3 Latest on outcome, within 3% of GPT-5.2's median, #4 overall behind Opus 4.6, GPT-5.2, and Grok 4.3.

The timing is the interesting part. We tested GPT-5.2 in mid-February. DeepSeek V4 Pro matches its numbers ten weeks later. The China–US frontier gap on this benchmark used to feel like a year. Right now it's about ten weeks.

The pricing gap is even sharper. GPT-5.2 charges $1.75/M input and $14/M output. DeepSeek V4 Pro is at $0.435/M input and $0.87/M output, with discounted cache reads on top — **\~17× cheaper for the same agentic workload**. That's promo pricing today, but DeepSeek's track record is that promo becomes the floor.

On cost-efficiency (net worth per dollar of API spend) DeepSeek V4 Pro is #2 overall on the leaderboard — behind only Gemma 4 31B, ahead of every premium-tier model.

Against Grok 4.3 Latest specifically the medians are basically tied at the same price, but DeepSeek wins on consistency: zero loans, \~6× less food waste, 30% more meals served per day, 2.4× tighter outcome distribution. Grok matches DeepSeek's peak. DeepSeek matches its own peak every time.

Opus 4.6's peak run is still higher than DeepSeek's. Gemma is still cheaper. Otherwise this is a real frontier-tier competitor at a Chinese price point.

**Update — Xiaomi MiMo v2.5 Pro just finished its run set as well:** 5/5 survived, +1,019% median ROI, $22,388 median net worth at $2.41/run. Lands at #6 on the leaderboard, between Gemma 4 31B and Sonnet 4.6. Slightly behind DeepSeek on outcome and consistency (wider variance — $9K worst run vs $29K best), but a real result for a Chinese model at this price point.

That's now two Chinese models in our top 6, both at sub-$3.5/run. When we started this benchmark in February, neither of these tiers existed outside US labs.

Congrats to the DeepSeek and Xiaomi MiMo teams.

Full write-up: [https://foodtruckbench.com/blog/deepseek-v4-pro](https://foodtruckbench.com/blog/deepseek-v4-pro)
Leaderboard: [https://foodtruckbench.com](https://foodtruckbench.com/)

Just wanted to share that I used u/LegacyRemaster slightly modified (Q4\_K\_M conversion support) DeepSeek V4 [CUDA repo](https://github.com/Fringe210/llama.cpp-deepseek-v4-flash-cuda) (based on u/antirez [work](https://github.com/antirez/llama.cpp-deepseek-v4-flash)) to convert and run Q4\_K\_M [DeepSeek V4 Pro](https://huggingface.co/deepseek-ai/DeepSeek-V4-Pro) on my Epyc workstation (Genoa 9374F, 12 x 96GB RAM, single RTX PRO 6000 Max-Q) and it worked right from the start:

(base) phm@epyc:~/projects/llama.cpp-deepseek-v4-flash-cuda/build-cuda$ ./bin/llama-cli -m ../models/DeepSeek-V4-Pro-Q4_K_M.gguf --no-repack -ub 128 --chat-template-file ../models/templates/deepseek-ai-DeepSeek-V3.2.jinja
ggml_cuda_init: found 1 CUDA devices (Total VRAM: 97247 MiB):
Device 0: NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition, compute capability 12.0, VMM: yes, VRAM: 97247 MiB

Loading model...

▄▄ ▄▄
██ ██
██ ██ ▀▀█▄ ███▄███▄ ▀▀█▄ ▄████ ████▄ ████▄
██ ██ ▄█▀██ ██ ██ ██ ▄█▀██ ██ ██ ██ ██ ██
██ ██ ▀█▄██ ██ ██ ██ ▀█▄██ ██ ▀████ ████▀ ████▀
██ ██
▀▀ ▀▀

build : b8936-44c7b01de
model : DeepSeek-V4-Pro-Q4_K_M.gguf
modalities : text

available commands:
/exit or Ctrl+C stop or exit
/regen regenerate the last response
/clear clear the chat history
/read <file> add a text file
/glob <pattern> add text files using globbing pattern

> who are you?

[Start thinking]
Okay, the user is asking "who are you?" This is a simple, introductory question. I need to introduce myself clearly and warmly. I should state my name, creator, and key features that are most relevant to a new user. I can mention that I'm free, my context window, knowledge cutoff, file support, and availability on web and app. I'll end with an open invitation for further questions to keep the conversation going.
[End thinking]

Hi there! I'm DeepSeek, an AI assistant created by the Chinese company DeepSeek (深度求索). I'm here to help you with questions, creative tasks, problem-solving, and pretty much anything you're curious about!

Here's a bit about me:
- **Free to use** - no charges for chatting with me
- **1M context window** - I can handle huge amounts of text at once (like entire book trilogies!)
- **Knowledge cutoff: May 2025** - I'm reasonably up-to-date
- **File upload support** - I can read text from images, PDFs, Word docs, Excel files, and more
- **Web search capability** - though you need to manually enable it via the search button
- **Available on web and mobile app** - with voice input support on the app

I'm a pure text-based model, so I can't "see" images directly, but I can read any text in uploaded files. I aim to be warm, helpful, and detailed in my responses.

What can I help you with today? 😊

[ Prompt: 12.2 t/s | Generation: 8.6 t/s ]

> /exit

Exiting...
common_memory_breakdown_print: | memory breakdown [MiB] | total free self model context compute unaccounted |
common_memory_breakdown_print: | - CUDA0 (RTX PRO 6000 Blackwell Max-Q Workstation Edition) | 97247 = 4022 + ( 92472 = 87766 + 84 + 4621) + 753 |
common_memory_breakdown_print: | - Host | 793994 = 793954 + 0 + 39 |
~llama_context: CUDA_Host compute buffer size of 39.1719 MiB, does not match expectation of 15.3535 MiB

The model file is 859GB.

Update: ran some lineage-bench prompts to see if the model has healthy brain and no problems so far.

In the `V3.2` paper, they mentioned:

>Second, token efficiency remains a challenge; DeepSeek-V3.2 typically requires longer generation trajectories (i.e., more tokens) to match the output quality of models like Gemini 3.0-Pro. Future work will focus on optimizing the intelligence density of the model’s reasoning chains to improve efficiency.

However, in `V4 Pro`, the situation seems to have worsened. Even the non-thinking mode uses significantly more tokens than `V3.2`, and `V4 Pro` (1.6T) is roughly 2.5x larger than `V3.2` (0.67T). This suggests that the intelligence density of the model has decreased rather than improved!

If we compare it with `GPT-5.4` and `GPT-5.5`, the gap is even larger. DeepSeek appears to require around 10x more tokens to achieve similar performance. Assuming the same TPS, this implies roughly 10x longer for DeepSeek V4 Pro to complete the same task.