Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

I tested MTPLX v2 with QWEN 3.6 27B and compared it with oMLX without cache on M5 Max and DGX Spark on vllm using nvfp4 model version. More details in 🧵 I've reached 82.8 tps of max decoding speed! 🔥 Custom Metal Kernel design specifically for this model and... show more

Ivan Fioravanti ᯅ

41,120 subscribers

15,885 просмотров • 2 месяцев назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Got DeepSeek V4 Flash running on 2x H200s at 160–200 tok/s on JarvisLabsAI this speed is perfect for in the loop things I do with these agents. It feels like a GLM-5.2-class model with much lower hardware requirements. I’m going to daily-drive it for a bit and see how it performs, but first impressions are really good.

Got DeepSeek V4 Flash running on 2x H200s at 160–200 tok/s on JarvisLabsAI this speed is perfect for in the loop things I do with these agents. It feels like a GLM-5.2-class model with much lower hardware requirements. I’m going to daily-drive it for a bit and see how it performs, but first impressions are really good.

Atharva Ingle

21,925 просмотров • 2 месяцев назад

Been using Qwen 3.8 27B (Q4) locally on 64GB of VRAM. Here is the verdict: SLOW 18 tps with ZERO system prompt to process and that degrades significantly with a harness system prompt and as the context window grows. RIP if you have to compact. I had it implement this PRD and it's been running for 6 hours. By comparison Grok 4.6 and Kimi K3 hosted finished in about ~30 minutes. High hopes, but these 27B variants are too dense. This is not a consumer grade local model - and I consider consumer grade to be anything up to $5000.

Been using Qwen 3.8 27B (Q4) locally on 64GB of VRAM. Here is the verdict: SLOW 18 tps with ZERO system prompt to process and that degrades significantly with a harness system prompt and as the context window grows. RIP if you have to compact. I had it implement this PRD and it's been running for 6 hours. By comparison Grok 4.6 and Kimi K3 hosted finished in about ~30 minutes. High hopes, but these 27B variants are too dense. This is not a consumer grade local model - and I consider consumer grade to be anything up to $5000.

Burke Holland

122,501 просмотров • 1 месяц назад

Manus AI is much crazier than Deepseek moment I just got invitation code, this thing is the craziest AI agent I've seen. 10 examples: 1. Clone Apple website It created a copy of Apple website that looks almost the same, with animations and all. (preview link in comment)

Manus AI is much crazier than Deepseek moment I just got invitation code, this thing is the craziest AI agent I've seen. 10 examples: 1. Clone Apple website It created a copy of Apple website that looks almost the same, with animations and all. (preview link in comment)

el.cine

1,128,475 просмотров • 1 год назад

Qwen just released Qwen-Image-2.1, and this is exactly why open models matter. I loaded it onto my NVIDIA DGX Spark and built Spark Image Lab, a local image generation and editing workspace designed for the DGX Spark ecosystem. QWEN-IMAGE-2.1 • Text-to-image generation • Image editing • Native transparent/RGBA workflows • Up to 10 reference images • Strong identity and product preservation • Improved typography, lighting, textures and detail SPARK IMAGE LAB • Clean Gradio interface • Width and height controls • Steps, seed and batch controls • Persistent generation history • Prompts and settings saved with every result • Reference images saved and restored • Docker setup for DGX Spark • Measured DGX Spark performance benchmarks Everything runs locally. Spark Image Lab is now open source under the MIT License. This is the first public alpha, so clone it, test it on your DGX Spark, open an issue and show me what you create. MODEL REPO

Qwen just released Qwen-Image-2.1, and this is exactly why open models matter. I loaded it onto my NVIDIA DGX Spark and built Spark Image Lab, a local image generation and editing workspace designed for the DGX Spark ecosystem. QWEN-IMAGE-2.1 • Text-to-image generation • Image editing • Native transparent/RGBA workflows • Up to 10 reference images • Strong identity and product preservation • Improved typography, lighting, textures and detail SPARK IMAGE LAB • Clean Gradio interface • Width and height controls • Steps, seed and batch controls • Persistent generation history • Prompts and settings saved with every result • Reference images saved and restored • Docker setup for DGX Spark • Measured DGX Spark performance benchmarks Everything runs locally. Spark Image Lab is now open source under the MIT License. This is the first public alpha, so clone it, test it on your DGX Spark, open an issue and show me what you create. MODEL REPO

Joey

23,578 просмотров • 14 дней назад

Nah no, this is not a pre-made or baked Blender model. It is created entirely from scratch using extruded geometry and procedural textures for the mustard hatching pattern on the model... all done with Google Gemini 3 pro AI. In fact, every Three.js 3D model you see on this website has been vibe coded with AI 😎 Live: Code:

Nah no, this is not a pre-made or baked Blender model. It is created entirely from scratch using extruded geometry and procedural textures for the mustard hatching pattern on the model... all done with Google Gemini 3 pro AI. In fact, every Three.js 3D model you see on this website has been vibe coded with AI 😎 Live: Code:

The Bugged Dev

54,391 просмотров • 8 месяцев назад

I gave the new Meta Muse Spark model a bunch of assorted assets and it was able to carefully extract them and place it into a functioning app. I've never seen something with a clear intuition for design and product-first thinking. This is the first AI that *gets* UI design.

I gave the new Meta Muse Spark model a bunch of assorted assets and it was able to carefully extract them and place it into a functioning app. I've never seen something with a clear intuition for design and product-first thinking. This is the first AI that gets UI design.

Michael G

38,924 просмотров • 5 месяцев назад

Mia Khalifa & Michael Scott A job interview from The Office, but with… Sorry, guys—I just had to do this 🤣🤣🤣 I created this entire video on MiniMax Design (H3) using MiniMax H3—with just a single prompt. This model is absolutely insane. I’ve been running a lot of tests, and I honestly haven’t had this much fun with a model in a very long time.

Mia Khalifa & Michael Scott A job interview from The Office, but with… Sorry, guys—I just had to do this 🤣🤣🤣 I created this entire video on MiniMax Design (H3) using MiniMax H3—with just a single prompt. This model is absolutely insane. I’ve been running a lot of tests, and I honestly haven’t had this much fun with a model in a very long time.

Riccardo Wolf

21,403 просмотров • 2 месяцев назад

Day 11/90 of Inference Engineering How does vLLM work and how is it used in production? Before we discuss how vLLM works internally, it helps to understand what vLLM is. At a high level, vLLM is an inference engine that is designed to serve LLMs to thousands of concurrent users efficiently while managing scarce compute and memory. The goal for vLLM is to maximize throughput and minimize latency; optimizing for the best inference economics and experience for end users. With every request from the end user, it eventually ends up in the engine core, gets scheduled alongside other requests from other concurrent users, executes on the GPU, and updates the KV cache with the new key and value vectors, and streams the tokens back to the user. The Scheduler decides what requests should execute next while continuously batching requests together to maximize GPU utilization. Continuous batching is an inference optimization that allows new requests to join a running batch as other requests finish generating tokens. This helps with keeping the GPU utilization high instead of letting it sit idle waiting for an entire batch to complete generating. After the scheduler dispatches the selected batch to the Model Executor, the Model Executor prepares the tensors and metadata required for inference, retrieves each request’s block table from KV Cache Manager, launches the optimized transformer forward pass on the GPU, computes the logits, updates the KV cache with the new key and value vectors, and finally returns the results for sampling and streaming. The KV Cache Manager uses the PagedAttention memory layout to allocate fixed-size cache blocks on demand and maintains a Free Block Queue on the CPU that tracks which blocks in the GPU’s Paged KV Cache are currently free. When a request needs additional KV cache space, the KV Cache manager takes a free block from the queue and assigns it to that request, thus avoiding an expensive search through GPU memory for available cache blocks. All of these components form the core of vLLM’s inference engine. The Scheduler determines what requests are executed, the Model Executor determines how those requests are executed, the KV Cache Manager determines where each request’s KV cache lives using the PagedAttention Memory Layout. This architecture enables vLLM to serve thousands of concurrent requests with high throughput, low latency, and efficient GPU memory utilization. Heres a little animation that visualizes everything! - I've also completed the forward pass for my mnist.c project. I had a nice chat with shrey birmiwal, such a knowledgeable guy. Excited to learn more about vLLM and implement a tiny-vLLM one day.

Day 11/90 of Inference Engineering How does vLLM work and how is it used in production? Before we discuss how vLLM works internally, it helps to understand what vLLM is. At a high level, vLLM is an inference engine that is designed to serve LLMs to thousands of concurrent users efficiently while managing scarce compute and memory. The goal for vLLM is to maximize throughput and minimize latency; optimizing for the best inference economics and experience for end users. With every request from the end user, it eventually ends up in the engine core, gets scheduled alongside other requests from other concurrent users, executes on the GPU, and updates the KV cache with the new key and value vectors, and streams the tokens back to the user. The Scheduler decides what requests should execute next while continuously batching requests together to maximize GPU utilization. Continuous batching is an inference optimization that allows new requests to join a running batch as other requests finish generating tokens. This helps with keeping the GPU utilization high instead of letting it sit idle waiting for an entire batch to complete generating. After the scheduler dispatches the selected batch to the Model Executor, the Model Executor prepares the tensors and metadata required for inference, retrieves each request’s block table from KV Cache Manager, launches the optimized transformer forward pass on the GPU, computes the logits, updates the KV cache with the new key and value vectors, and finally returns the results for sampling and streaming. The KV Cache Manager uses the PagedAttention memory layout to allocate fixed-size cache blocks on demand and maintains a Free Block Queue on the CPU that tracks which blocks in the GPU’s Paged KV Cache are currently free. When a request needs additional KV cache space, the KV Cache manager takes a free block from the queue and assigns it to that request, thus avoiding an expensive search through GPU memory for available cache blocks. All of these components form the core of vLLM’s inference engine. The Scheduler determines what requests are executed, the Model Executor determines how those requests are executed, the KV Cache Manager determines where each request’s KV cache lives using the PagedAttention Memory Layout. This architecture enables vLLM to serve thousands of concurrent requests with high throughput, low latency, and efficient GPU memory utilization. Heres a little animation that visualizes everything! - I've also completed the forward pass for my mnist.c project. I had a nice chat with shrey birmiwal, such a knowledgeable guy. Excited to learn more about vLLM and implement a tiny-vLLM one day.

max fu

70,797 просмотров • 2 месяцев назад

My dual RTX PRO 6000 setup is currently training a Draft model for Qwen 3.6 27B! 🔥 I'm taking the paper DeepSeek dropped on 6/26 and going for a super ambitious application to the 27B scale. Thanks to my homelab, I was able to dive straight in — I read the paper and immediately started experimenting. The amount I've learned has been insane: - How memory bandwidth bottlenecks speed and clever ways to hack around it - Methods to train the draft model and boost its accuracy - Mechanisms to reference tokens all the way back to the previous one to skyrocket draft acceptance rates - The impact of Attention vs. GateDeltaNet on speculative decoding performance and how to handle those differences - The unique approaches and trade-offs of MTP, Dflash, JetSpec, and DSpark I could go on forever, but just from speculative decoding alone I've learned so much. The 27B architecture feels way more DSpark-native than JetSpec, so once draft training finishes, I'm going all-in with DSpark! My goal is to beat existing speculative decoding speeds outright — no task-specific shortcuts or cheating, pure general improvement. If you're into this kind of research, I'd love to hear your thoughts, impressions, and any suggestions — please reply! 🚀

My dual RTX PRO 6000 setup is currently training a Draft model for Qwen 3.6 27B! 🔥 I'm taking the paper DeepSeek dropped on 6/26 and going for a super ambitious application to the 27B scale. Thanks to my homelab, I was able to dive straight in — I read the paper and immediately started experimenting. The amount I've learned has been insane: - How memory bandwidth bottlenecks speed and clever ways to hack around it - Methods to train the draft model and boost its accuracy - Mechanisms to reference tokens all the way back to the previous one to skyrocket draft acceptance rates - The impact of Attention vs. GateDeltaNet on speculative decoding performance and how to handle those differences - The unique approaches and trade-offs of MTP, Dflash, JetSpec, and DSpark I could go on forever, but just from speculative decoding alone I've learned so much. The 27B architecture feels way more DSpark-native than JetSpec, so once draft training finishes, I'm going all-in with DSpark! My goal is to beat existing speculative decoding speeds outright — no task-specific shortcuts or cheating, pure general improvement. If you're into this kind of research, I'd love to hear your thoughts, impressions, and any suggestions — please reply! 🚀

Hikari∣LocalLLM⚡

56,870 просмотров • 3 месяцев назад

Okay, I am fairly confident in my hypothesis now. The secret sauce behind Qwen 3.8 27B becomes almost immediately evident during testing. It is not the training data. In fact, I doubt any SFT was involved at all. The model was simply allowed GRPO with a more liberal reasoning context length. As I have explained to you before, distillation through GRPO is powerful, and in certain contexts vastly superior to K/L divergence distillation. Qwen used the outputs of Qwen 3.8 Max as the reinforcement learning objective for Qwen 3.8 27B and told the model reason as much as it has to in order to match the output. Remember, Intelligence is solution, not compression. This is like nesting the output of a function as an additional input to itself, and it is absolutely brilliant.

Okay, I am fairly confident in my hypothesis now. The secret sauce behind Qwen 3.8 27B becomes almost immediately evident during testing. It is not the training data. In fact, I doubt any SFT was involved at all. The model was simply allowed GRPO with a more liberal reasoning context length. As I have explained to you before, distillation through GRPO is powerful, and in certain contexts vastly superior to K/L divergence distillation. Qwen used the outputs of Qwen 3.8 Max as the reinforcement learning objective for Qwen 3.8 27B and told the model reason as much as it has to in order to match the output. Remember, Intelligence is solution, not compression. This is like nesting the output of a function as an additional input to itself, and it is absolutely brilliant.

Aesther

123,124 просмотров • 1 месяц назад

Introducing Jan v3, with updates to Jan Desktop v0.7.6 💛 Jan v3 is our first v3 model, a 4B base built for fine-tuning and fast local use, with stronger math and coding. This release also includes a small Jan Desktop update, starting with a UI refresh as we move toward a more unified Jan experience. Try it: - Jan v3 is available in Jan Desktop and at - Get the latest desktop app at Model: - Jan-v3-4B: - Jan-v3-4B-GGUF: Thanks Qwen for the base model and Georgi Gerganov for llama.cpp 💛

Introducing Jan v3, with updates to Jan Desktop v0.7.6 💛 Jan v3 is our first v3 model, a 4B base built for fine-tuning and fast local use, with stronger math and coding. This release also includes a small Jan Desktop update, starting with a UI refresh as we move toward a more unified Jan experience. Try it: - Jan v3 is available in Jan Desktop and at - Get the latest desktop app at Model: - Jan-v3-4B: - Jan-v3-4B-GGUF: Thanks Qwen for the base model and Georgi Gerganov for llama.cpp 💛

👋 Jan

53,900 просмотров • 8 месяцев назад

/1 Gemma 4 31B just crushed Qwen 3.6 27B in a local LLM gamedev contest inside atomic.chat (prompt is below) Device: MacBook Pro M5 Max, 64GB RAM Results: Qwen 3.6 27B: 32 tokens/sec · 18m 04s · 33,946 tokens Gemma 4 31B: 27 tokens/sec · 3m 51s · 6,209 tokens So what is more important: tokens per second, or the quality of the final answer? Qwen made a very long response and showed more creativity and visual style. But Gemma gave a shorter, clearer, and more logical answer in much less time. In this one-shot Pac-Man gamedev contest, Gemma 4 31B was the clear winner. Its game logic was stronger: click reactions were smoother, and it handled interactions with elements like walls, ghosts, and particle effects better. But this was only one test. Maybe Qwen 3.6 27B can show better results with better settings. Open the comments, try our prompt, and share your result below.

/1 Gemma 4 31B just crushed Qwen 3.6 27B in a local LLM gamedev contest inside atomic.chat (prompt is below) Device: MacBook Pro M5 Max, 64GB RAM Results: Qwen 3.6 27B: 32 tokens/sec · 18m 04s · 33,946 tokens Gemma 4 31B: 27 tokens/sec · 3m 51s · 6,209 tokens So what is more important: tokens per second, or the quality of the final answer? Qwen made a very long response and showed more creativity and visual style. But Gemma gave a shorter, clearer, and more logical answer in much less time. In this one-shot Pac-Man gamedev contest, Gemma 4 31B was the clear winner. Its game logic was stronger: click reactions were smoother, and it handled interactions with elements like walls, ghosts, and particle effects better. But this was only one test. Maybe Qwen 3.6 27B can show better results with better settings. Open the comments, try our prompt, and share your result below.

Chubby♨️

72,566 просмотров • 5 месяцев назад

1/ Gemini 2.5 is here, and it’s our most intelligent AI model ever. Our first 2.5 model, Gemini 2.5 Pro Experimental is a state-of-the-art thinking model, leading in a wide range of benchmarks – with impressive improvements in enhanced reasoning and coding and now #1 on Arena by a significant margin. With a model this intelligent, we wanted to get it to people as quickly as possible. Find it on Google AI Studio and in the Google Gemini for Gemini Advanced users now – and in Vertex in the coming weeks. This is the start of a new era of thinking models – and we can’t wait to see where things go from here.

1/ Gemini 2.5 is here, and it’s our most intelligent AI model ever. Our first 2.5 model, Gemini 2.5 Pro Experimental is a state-of-the-art thinking model, leading in a wide range of benchmarks – with impressive improvements in enhanced reasoning and coding and now #1 on Arena by a significant margin. With a model this intelligent, we wanted to get it to people as quickly as possible. Find it on Google AI Studio and in the Google Gemini for Gemini Advanced users now – and in Vertex in the coming weeks. This is the start of a new era of thinking models – and we can’t wait to see where things go from here.

Sundar Pichai

864,841 просмотров • 1 год назад

Meet the new look of Cluely. ~1,200 hours, and 3 months of teamwork dedicated to the exploration of the look, design, motion, and development of the new website for the most viral startup. The main challenge was to achieve a "generalized" look while having something special, so the site could be practical and efficient for any type of audience. I hope we succeeded with this. Stay tuned for a massive project breakdown later this month on YT. PS: Roy is a great guy and super easy to work with. The best client ever.

Meet the new look of Cluely. ~1,200 hours, and 3 months of teamwork dedicated to the exploration of the look, design, motion, and development of the new website for the most viral startup. The main challenge was to achieve a "generalized" look while having something special, so the site could be practical and efficient for any type of audience. I hope we succeeded with this. Stay tuned for a massive project breakdown later this month on YT. PS: Roy is a great guy and super easy to work with. The best client ever.

Alex Barashkov

632,675 просмотров • 1 год назад

I just tested the Hitem3D V2.0 Beta It captures complex details with true print-grade geometry. We’re talking ready for 3D printing, CNC, and even laser cutting straight out of generation. Look at this incredible result down below. On the left side the image, on the right side the 3D Model

I just tested the Hitem3D V2.0 Beta It captures complex details with true print-grade geometry. We’re talking ready for 3D printing, CNC, and even laser cutting straight out of generation. Look at this incredible result down below. On the left side the image, on the right side the 3D Model

Chubby♨️

64,565 просмотров • 9 месяцев назад

Astra (GPT-6) is here!!! I've had early access and tested it like crazy with things like games, code, writing, browser control, presentations and general knowledge work. This is the best model I've ever used. Period. (Incredible demos below in this thread ⬇️) Here's my take on Astra: > It's insanely capable. This feels like a massive improvement, not just an incremental change. This is especially true with zero-shot prompts. > It's all about knowledge work. Slide creation, analysis, writing, and browser control. And oh my...it's so good at browser control. GPT-5.6 was already fantastic at doing things in the browser, Astra is another level and significantly faster. > We're closer than ever (arrived?) at prompt-to-playable game. And I don't just mean only playable, these are actually fun games. I bet if someone with a great eye for games used Astra, they could create a viral game within 1-2 weeks. > Astra is better at writing but not perfect. It removes much of the "AI Smell" we're all familiar with but some stink still survived. > It has a tendency to use the same design colors and look/feel as GPT-5.6 (forrest green anyone?) but it is more steerable in design than previous models. > It's highly steerable in general. A little nudge goes a long way. When I first started using Astra, almost every task I gave it would go for ~30 minutes. I wanted it to keep working. Adding more specifics to a prompt helped greatly with it's ability to work for a long time. > Astra's 3D understanding is unmatched. 3D asset creation was consistent and easy and its spacial awareness while building complex 3D worlds blew me away. I'm still getting familiar with Astra but this will now be my go-to model for any difficult work I have. Check out the demos below: 👇

Astra (GPT-6) is here!!! I've had early access and tested it like crazy with things like games, code, writing, browser control, presentations and general knowledge work. This is the best model I've ever used. Period. (Incredible demos below in this thread ⬇️) Here's my take on Astra: > It's insanely capable. This feels like a massive improvement, not just an incremental change. This is especially true with zero-shot prompts. > It's all about knowledge work. Slide creation, analysis, writing, and browser control. And oh my...it's so good at browser control. GPT-5.6 was already fantastic at doing things in the browser, Astra is another level and significantly faster. > We're closer than ever (arrived?) at prompt-to-playable game. And I don't just mean only playable, these are actually fun games. I bet if someone with a great eye for games used Astra, they could create a viral game within 1-2 weeks. > Astra is better at writing but not perfect. It removes much of the "AI Smell" we're all familiar with but some stink still survived. > It has a tendency to use the same design colors and look/feel as GPT-5.6 (forrest green anyone?) but it is more steerable in design than previous models. > It's highly steerable in general. A little nudge goes a long way. When I first started using Astra, almost every task I gave it would go for ~30 minutes. I wanted it to keep working. Adding more specifics to a prompt helped greatly with it's ability to work for a long time. > Astra's 3D understanding is unmatched. 3D asset creation was consistent and easy and its spacial awareness while building complex 3D worlds blew me away. I'm still getting familiar with Astra but this will now be my go-to model for any difficult work I have. Check out the demos below: 👇

Matthew Berman

1,907,752 просмотров • 1 месяц назад

I finally got GLM-5.2 to work an entire 3-year patient chart that only Bonsai 27B was allowed to read 🔥 292 encounters live inside Bonsai on my Mac Studio. llama.cpp, Metal, ternary, 7.2GB, Apache-2.0. The chart never leaves the machine. GLM-5.2 can only ask questions. It asked three. Bonsai answered each in ~2s with 19,398 tokens still cached. Then it caught the thing buried 17 months back: metformin + iodinated contrast at eGFR 39. Nephrology warned about it in 2025. The ED booked the CT anyway. A 27B-class model used to need a datacentre. PrismML say the 1-bit build is 3.9GB and fits an iPhone 17 Pro Max. The orchestrator never touched the data. That's the whole point. What should it read next?

I finally got GLM-5.2 to work an entire 3-year patient chart that only Bonsai 27B was allowed to read 🔥 292 encounters live inside Bonsai on my Mac Studio. llama.cpp, Metal, ternary, 7.2GB, Apache-2.0. The chart never leaves the machine. GLM-5.2 can only ask questions. It asked three. Bonsai answered each in ~2s with 19,398 tokens still cached. Then it caught the thing buried 17 months back: metformin + iodinated contrast at eGFR 39. Nephrology warned about it in 2025. The ED booked the CT anyway. A 27B-class model used to need a datacentre. PrismML say the 1-bit build is 3.9GB and fits an iPhone 17 Pro Max. The orchestrator never touched the data. That's the whole point. What should it read next?

Maziyar PANAHI

53,811 просмотров • 2 месяцев назад

A quick test of using 3d drawing with 6DOF controllers as an "instructor" for a generative AI process. There's so many powerful and fun new ways to create just around the corner.. Here I'm using Dreams, Krea and 3daistudio. The 3d model at the end of the video was generated from the Dreams+Krea output in just around 15 seconds. Only the model on the left is a "true" 3d model. #ai #madeindreams

A quick test of using 3d drawing with 6DOF controllers as an "instructor" for a generative AI process. There's so many powerful and fun new ways to create just around the corner.. Here I'm using Dreams, Krea and 3daistudio. The 3d model at the end of the video was generated from the Dreams+Krea output in just around 15 seconds. Only the model on the left is a "true" 3d model. #ai #madeindreams

Martin Nebelong

132,897 просмотров • 2 лет назад

Salute to the Qwen team 🫡 We tested Qwen 3.7-Max, Gemini 3.5 Flash, GPT-5.5, and Claude Opus 4.7. The biggest shock came from Qwen. In less than a month (3.6 Max dropped April 20), Qwen went from the worst multimodal output on our sakura tree test, barely keeping up with Gemini, GPT, and Claude , to matching Gemini 3.5 Flash frame for frame on this soccer test, and outperforming GPT-5.5 and Claude Opus 4.7. It rendered a perfectly proportioned soccer player and the most lifelike ball in the entire test. Remarkable spatial reasoning. Also: Gemini 3.5 Flash is now faster than GPT-5.5, which used to be the fastest in our past tests.

Salute to the Qwen team 🫡 We tested Qwen 3.7-Max, Gemini 3.5 Flash, GPT-5.5, and Claude Opus 4.7. The biggest shock came from Qwen. In less than a month (3.6 Max dropped April 20), Qwen went from the worst multimodal output on our sakura tree test, barely keeping up with Gemini, GPT, and Claude , to matching Gemini 3.5 Flash frame for frame on this soccer test, and outperforming GPT-5.5 and Claude Opus 4.7. It rendered a perfectly proportioned soccer player and the most lifelike ball in the entire test. Remarkable spatial reasoning. Also: Gemini 3.5 Flash is now faster than GPT-5.5, which used to be the fastest in our past tests.

GMI Cloud

75,785 просмотров • 4 месяцев назад