# Using High-Cost Models for Low-Complexity Tasks

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/using-high-cost-models-for-low-complexity-tasks-bec92

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Using High-Cost Models for Low-Complexity Tasks

## Explanation

Vertex AI workloads often include low-complexity tasks such as classification, routing, keyword extraction, metadata parsing, document triage, or summarization of short and simple text. These operations do \*\*not\*\* require the advanced multimodal reasoning or long-context capabilities of larger Gemini model tiers. When organizations default to a single high-end model (such as Gemini Ultra or Pro) across all applications, they incur elevated token costs for work that could be served efficiently by \*\*Gemini Flash\*\* or smaller task-optimized variants. This mismatch is a common pattern in early deployments where model selection is driven by convenience rather than workload-specific requirements. Over time, this creates unnecessary spend without delivering measurable value.

## Relevant Billing Model

Generative AI usage is billed per input and output token. Larger, more capable models (e.g., Gemini Ultra or Pro) have significantly higher cost per token compared to smaller models optimized for fast, lightweight tasks. Choosing a model that exceeds workload requirements increases spend without improving output quality.

## Detection

- Identify workloads performing simple or deterministic tasks that do not require advanced generative reasoning

- Review model selections across projects to find consistent use of high-cost models as global defaults

- Assess token consumption patterns for repetitive or structured inference where lighter models would suffice

- Evaluate whether output quality, accuracy, or latency requirements can be met by lower-tier models

- Determine whether teams lack model selection guidelines or rely on a "one model fits all" pattern

## Remediation

- Select the smallest Vertex AI model tier that satisfies accuracy, latency, and quality requirements

- Use Gemini Flash or other lightweight model variants for classification, extraction, routing, and similar simple tasks

- Establish internal model selection standards to prevent unnecessary use of premium models

- Periodically re-evaluate deployed model choices as new Gemini model tiers and optimizations are released

- Validate functional behavior after model right-sizing to ensure quality remains acceptable

## Relevant Documentation

[Submit Feedback](https://hub.pointfive.co/inefficiencies/using-high-cost-models-for-low-complexity-tasks-bec92)

## At a glance

Reference

CER-0267

Cloud provider

GCP

Service

GCP Vertex AI

Category

[AI](https://www.pointfive.co/efficiency-hub/service-category/ai)

Inefficiency type

Overpowered Model Selection

## Contributed by

- Taylor Houck 

### Taylor Houck

Cloud FinOps Specialist @ PointFive

[LinkedIn](https://www.linkedin.com/in/twhouck/)

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.