Tabbit
ResourcesBlogModels
Tabbit LogoTabbit

Tabbit — The AI Browser that Works for You

Topics

  • AI Browser Resources
  • Agentic Browser Resources
  • Browser Downloads and Install Guides
  • Browser Comparisons
  • AI Browser Alternatives
  • Browser Productivity Resources

Popular Guides

  • AI Browser
  • Agentic Browser Download
  • Best AI Browser 2026: Top 9 Tested & Ranked
  • AI Browser Download
  • Free AI Browser
  • Best AI Browser 2026
  • AI Browser Comparison 2026
  • AI Browser for Windows
  • AI Browser for Mac
  • Chrome Alternative 2026

Events

  • Tabbit Skill Competition
  • KPOP SBTI Fandom Personality Test
  • Tabbit Campus Creator Program
  • fifi's Picks: AI Skills for Research Papers
  • User Survey

About

  • Tabbit Blog
  • Press & Media
English
简体中文English
Reviews and evidence

Qwen3.5 Plus · Media / benchmark · Independent measurement

Qwen3.5-Plus: Qubrid's Same-Image, Same-Prompt Latency and Token Comparison

Qubrid records latency, token allocation, and output differences in one same-image, same-prompt run; the backend snapshot is undisclosed, so the result is Playground-specific.

Unverified: the original source could not be rechecked. Historical figures below are not current verified results.

Media / benchmarkIndependent measurementEdited 2026-09-20

Test conditions

Source-specific observation
Qubrid compares Qwen3.5 Plus and Qwen3.6 Plus with the same image and prompt and records TTFT, total time, tokens/s, and token categories.
Published conditions
It reports 1,858 reasoning tokens out of 2,036 completion tokens for Qwen3.5 Plus; provider snapshot, repeats, and the full harness are unpublished.

Key data and applicable tasks

One-sentence takeaway

In Qubrid's single-run Playground vision test, Qwen3.5-Plus had a faster time to first token and total response, but spent most completion tokens on reasoning and produced shorter output text; this does not establish quality for all tasks.

Use cases

  • Suitable tasks: Initial screening where visual input, low latency, and raw generation speed matter; also reproducing a baseline with the same image, prompt, and provider.

  • Unsuitable tasks: Using one image and one run to prove complex Agent, long-context, or coding ability; or comparing latency and tokens across providers.

  • Applicable model versions: Qwen/Qwen3.5-Plus in Qubrid Playground; the specific backend snapshot was not disclosed.

  • Applicable clients, Agents, or APIs: Qubrid AI Playground; the article also provides an example for Qubrid's OpenAI-compatible interface.

  • Recommended reasoning level and parameters: For Qwen3.5-Plus, the article recommends temperature=0.6 and top_p=0.95; this is the article's provider configuration recommendation, not a recommendation from Alibaba Cloud's official model page.

Test environment

  • Platform: Qubrid AI Playground, Vision mode.

  • Input: The same image of “an origami boat on a blue-gray surface”; the user prompt was Describe what you see in this image..

  • Configuration: Model Reasoning was enabled for both models; the article records prompt tokens, completion tokens, reasoning tokens, output-text tokens, TTFT, total duration, and tokens/s.

  • Comparison: Qwen 3.5 Plus and Qwen 3.6 Plus; this article focuses on the original observations for Qwen3.5-Plus.

Input/configuration

Visual input: the same origami boat image
User prompt: Describe what you see in this image.
Model Reasoning: True
Model: Qwen/Qwen3.5-Plus

Results

MetricQwen3.5-PlusQwen3.6-Plus (comparison)
Total response time26.02 s40.03 s
TTFT6.86 s6.93 s
Completion tokens2,0361,613
Reasoning tokens1,8581,343
Output-text tokens178270
Tokens/s106.2738.32
Prompt tokens5,1115,117
Response structureStreaming paragraphsHeaded sections

Calculated from the article's data, reasoning tokens account for approximately 91.3% of Qwen3.5-Plus's completion tokens (1,858/2,036), and output text accounts for approximately 8.7%; this is the allocation in that run, not a fixed model ratio.

Conclusion

This case supports a narrow conclusion: in Qubrid's single-run, same-image, same-prompt test, Qwen3.5-Plus had lower total latency and higher generation speed than the comparison model, but its answer text was shorter and its reasoning share was higher. Production Agent evaluation should continue with tool-call success, structured output, repeatability, and long-context retrieval.

Limitations

  • The article does not disclose the image file, random seed, complete backend snapshot, concurrency, hardware, or number of repetitions; strictly speaking, only an approximate experiment can be reproduced from the public steps.

  • Timing and token statistics from the Qubrid provider cannot directly represent Alibaba Cloud Bailian's native endpoint.

  • The article's table extends Qwen3.5-Plus's multimodal description to audio, while Alibaba Cloud's official model page lists text, image, and video as inputs; this conflict should be resolved in favor of the official capability table, and audio capability should not be presented as verified fact.

Reproduction steps

  1. Select Qwen/Qwen3.5-Plus in Qubrid Playground and enter Vision mode.

  2. Upload the same origami boat image, enter the exact same English description prompt, and enable Model Reasoning.

  3. Save one complete response along with the TTFT, total duration, and token details shown by the page; do not record only the final text.

  4. Repeat at least 5 times, then report the mean, standard deviation, and failure count; if switching to the Bailian API, label the provider and model snapshot separately.

Source excerpt or observation (for a compliant short quotation only)

The article's reproducible input is “Describe what you see in this image.”, and it explicitly records a 26.02-second total response, 6.86-second TTFT, and 1,858 reasoning tokens; this article preserves the provider boundary.

What this supports

  • It supports a local migration test that includes latency and token instrumentation.

What this does not support

  • It cannot prove general agent, long-context, or code quality from one image task or extrapolate across providers.

Method, limits, and reproduction

The figures, task set, reasoning tier, and client conditions apply only to the listed source and collection snapshot. Different versions, harnesses, or providers must not be compared directly; undisclosed parameters remain unknown.

For a reproduction, fix the model version, provider or client, reasoning tier, tools, task-set version, sample count, and collection date, and record failures, retries, and human corrections. Full steps are in the source notes below.

Original source

Qubrid AI Blog · Qubrid AI (the page does not list an individual author) · Original publication date Unknown · Site edit date 2026-09-20

Open original source

Qwen3.5 Plus

Compare Qwen3.5 Plus in Tabbit

Download the Tabbit client to check model access

Read the full analysis

Overview · English

Qwen3.5 Plus: What It Is, What It Costs, and Where It Fits

A sourced Qwen3.5 Plus overview explaining its hosted/open-weight relationship, multimodal and tool boundaries, tiered 1M-context pricing, access routes, and safer pilot.

Related reviews

Qwen3.5-Plus: Digital Applied's Cross-Model Benchmarks and Hosted/Open-Weight SelectionDigital Applied summarizes Qwen3.5 benchmarks, API migration, and hosted-versus-open-weight tradeoffs; it has no uniform item-level harness and is best treated as an independent synthesis.Qwen3.5-Plus: Qwen's Official Native Multimodal Agent Release BaselineIt positions Qwen3.5 Plus as the hosted API counterpart to Qwen3.5-397B-A17B, covering vision, multimodal agents, tool calls, and a million-token context; the tables remain bounded by Alibaba’s harness.Qwen3.5-Plus: Alibaba Cloud Model Studio multimodal, long-context, and tool-calling configurationAlibaba Cloud lists Qwen3.5 Plus text, image, and video input, function calling, structured output, and a million-token context as integration boundaries.Qwen3.5-Plus: Pre-Tool-Call Reasoning Prompt (A Proposal to Validate Across Qwen3.5 Variants)A LocalLLaMA case turns pre-tool task decomposition, argument checks, and result review into a reusable Qwen3.5 Plus workflow; it is community practice, not a default system instruction.