Frequency Optimization
Identify tables that are refreshed far more often than they are read and reduce pipeline frequency to save compute.
Overview
Frequency Optimization surfaces tables whose write frequency significantly exceeds their read frequency. When a table is refreshed every hour but only queried once a day, the excess pipeline runs are wasted compute. Reducing the refresh cadence saves money without impacting consumers.
How It Works
Detection Logic
Seemore analyzes query history to build a read/write frequency profile for each table. A table is flagged when:
High write frequency — the table receives regular INSERT, MERGE, or COPY operations.
Low read frequency — SELECT activity is significantly less frequent than writes.
Sustained gap — there are sequences of 4 or more consecutive hours with write activity but no reads, indicating a pattern rather than a one-time spike.
Source and Destination Analysis
Seemore evaluates tables in two roles:
As a source (reads) — how often the table is queried by downstream consumers.
As a destination (writes) — how often the table is refreshed by upstream pipelines.
The ratio between these two frequencies determines the optimization opportunity.
Savings Estimation
Each insight includes:
Current refresh frequency and recommended frequency based on actual read patterns.
Estimated annual compute savings from reducing pipeline cadence.
Storage savings from fewer intermediate writes.
Remediation
Review the suggested frequency reduction in the insight detail.
Adjust the pipeline schedule (dbt job, Airflow DAG, Fivetran sync frequency) to match the recommended cadence.
Monitor downstream consumers for any impact.
Mark the insight as Done once the schedule is updated.
Configuration
Analysis window
21 days
How far back Seemore analyzes read/write patterns.
Minimum write gap
4 hours
Consecutive hours of writes without reads required to flag a table.
Last updated