Updated September 24, 2026. Rank says Gemini 1.5 Pro is ahead. Price, access, and your workload can each overturn that. Public scores include evidence status and uncertainty.
Both of these models will change. Get the price, version and retirement notices for the pair, each with its source. Follow model changes
The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. Use the documented cost, context, and runtime rows instead. 0 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.
NVIDIA
19.1/100
Estimated · Public rank #186
90% interval 9.2–29.0
Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.
No workload recommendation clears the current evidence threshold.
Use the matched evidence, workload costs, and sourced specifications below instead of treating a point score as a universal answer.
Code generation, repair, and software-engineering tasks
Not enough matched evidence
Gemini 1.5 Pro and Nemotron 3.5 Lightning 30B A3B NVFP4 are scored on Estimated evidence for coding, so the reading is directional rather than like-for-like.
Tool use, computer use, and multi-step task completion
Not enough matched evidence
Gemini 1.5 Pro is not ranked on the public lane for agentic, so no winner is named for agentic.
Prompts that approach the documented context limit
No clear pick
The documented context windows are equal.
1K fresh input + 500 output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
200K cached + 20K fresh input + 10K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
50K fresh input + 3K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Choose a job from the LLM Selector's task catalog to see the category row it rests on, under the same basis rules as the table below. A directional row stays directional; choosing a job never creates a winner.
The same task catalog as the LLM Selector. Each job names the evidence surface it rests on; nothing here adds a new score.
Directional only · BenchAlign v5.7
Gemini 1.5 Pro scores higher, but at least one score rests on Estimated evidence or a different benchmark set. Directional only, no winner.
Coding scores combine specific tasks and setups. Match the editor, harness, and effort to your workflow.
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
2 categories rest on Estimated evidence or different evidence sets. Those rows remain visible for coverage context but do not name a winner.
Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.
A shared-evidence shape is not available.
BenchLM does not draw a radar or infer missing axes when the matched evidence is too sparse.
Each row shows the public-lane category score for both models: the BenchAlign v5.7 lane for agentic, coding, and knowledge, and the weighted public rows elsewhere, with the same rank each model page reports. A row is like-for-like only when both scores rest on Supported evidence or the same weighted set. Directional and not-comparable rows remain visible, but they never receive a winner.
| Category | Gemini 1.5 Pro | Nemotron 3.5 Lightning 30B A3B NVFP4 | Basis | Reading |
|---|---|---|---|---|
| Coding | 22.4Estimated · #109/135 | 11.4Estimated · #135/135 | Directional onlyBenchAlign v5.7 lane · 0 vs 4 public rows | Directional only |
| Knowledge | 30.1Estimated · #129/158 | 20.7Estimated · #154/158 | Directional onlyBenchAlign v5.7 lane · 0 vs 4 public rows | Directional only |
| Agentic | Not ranked | 7.3Estimated · #104/105 | Not comparableBenchAlign v5.7 lane · 0 vs 4 public rows | Not comparable |
| Reasoning | Not ranked | 55.9Unranked · 1 rankable row | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Multimodal | 41.1Unranked · 1 rankable row | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Multilingual | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Instruction following | Not ranked | 68.5#67/124 | Not comparableProvisional lane · 0 vs 1 weighted rows | Not comparable |
| Math | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
Ranks count the models scored in each category’s lane, so the agentic, coding, and knowledge denominators (BenchAlign v5.7) differ from the provisional-lane categories. Unranked scores sit on the provisional lane’s scale but never name a winner. Like-for-like rows within 0.5 points read as a practical tie.
Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.
1K fresh input + 500 output tokens
Nemotron 3.5 Lightning 30B A3B NVFP4 has no comparable published API token rate.
50K fresh input + 3K output tokens
Nemotron 3.5 Lightning 30B A3B NVFP4 has no comparable published API token rate.
200K cached + 20K fresh input + 10K output tokens
Gemini 1.5 Pro has no published cached-input rate, so cached tokens use its listed input rate. Nemotron 3.5 Lightning 30B A3B NVFP4 has no comparable published API token rate.
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
Maximum documented context; output-token limits may be lower.
Gemini 1.5 Pro
1M
Nemotron 3.5 Lightning 30B A3B NVFP4
Gemini 1.5 Pro
Not sourced
Nemotron 3.5 Lightning 30B A3B NVFP4
Not sourced
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
Gemini 1.5 Pro
Not published
Nemotron 3.5 Lightning 30B A3B NVFP4
No comparable hosted API rate
NVIDIA Nemotron 3.5 Lightning model cardGemini 1.5 Pro
Not sourced
Nemotron 3.5 Lightning 30B A3B NVFP4
Not sourced
Gemini 1.5 Pro
Not sourced
Nemotron 3.5 Lightning 30B A3B NVFP4
Not sourced
Gemini 1.5 Pro
Not sourced
Nemotron 3.5 Lightning 30B A3B NVFP4
Not sourced
Gemini 1.5 Pro
Non-Reasoning
Nemotron 3.5 Lightning 30B A3B NVFP4
Reasoning
Gemini 1.5 Pro
Proprietary
Nemotron 3.5 Lightning 30B A3B NVFP4
Open Weight
Gemini 1.5 Pro
Proprietary
Nemotron 3.5 Lightning 30B A3B NVFP4
Open Weight
Gemini 1.5 Pro
2024-02-15
Nemotron 3.5 Lightning 30B A3B NVFP4
2026-08-11
The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. The page therefore keeps the decision tied to the specific documented workload.
Gemini 1.5 Pro scores higher for coding on the public lane, 22.4 to 11.4. Gemini 1.5 Pro and Nemotron 3.5 Lightning 30B A3B NVFP4 are scored on Estimated evidence for coding, so the reading is directional rather than like-for-like. BenchLM does not name a winner for coding from a directional reading; read the shared benchmark rows directly and test the models on the same task set.
Gemini 1.5 Pro is not ranked on the public lane for agentic tasks, so no winner is named for agentic tasks.
Both models do not have comparable published API token rates, so this page does not name a universal price winner.
Both models list the same context window, 1M.
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
Terminal-Bench 2.1
Not directly comparable
PinchBench
Not directly comparable
BrowseComp
Not directly comparable
τ³-bench results
Not directly comparable
SWE-bench Verified
Not directly comparable
SWE Multilingual
Not directly comparable
Terminal-Bench 2.1
Not directly comparable
SciCode
Not directly comparable
GPQA
Not directly comparable
GPQA-D
Not directly comparable
HLE w/o tools
Not directly comparable
MMLU-Pro
Not directly comparable
IFBench
Not directly comparable
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.
Last updated September 24, 2026
