typeahead stats
monthly cost · attribution in progress
Fly only. Typeahead’s share of shared services is still being calculated; this is not the total operating estimate.
Account subscriptions are not assigned wholly to Typeahead. R2, Logfire, and home power also remain unattributed.
what that runs · 24 hours ending Sep 5, 23:00 UTC
Turso · Typeahead usage within a shared account
The $45.40 September invoice covers the whole account, including the standard site index and other services. It is excluded from Typeahead’s estimate until costs are attributed.
| Database | Rows read | Rows written |
|---|---|---|
| typeahead | 523,390,116 | 19,902,224 |
| leaf | 296,327,134 | 480,272 |
| marvin-threads | 404,071 | 0 |
| foo | 0 | 0 |
Per-database values from the supplied screenshot. Reads and writes are different meters; their shares are not shares of the invoice.
The earlier 11.3 / 24 GB sync figure is account-wide. We still need per-database storage, sync bytes, billing dates, and overage line items.
Keep direct overages separate from an explicitly chosen share of the base subscription. Incremental cost asks how much lower the account bill would be without Typeahead; allocated cost also includes a share of the subscription.
Fly · current spending rate
$6.97 across both apps for Aug 30–Sep 5 × 30 / 7 = $29.87. This window includes architecture changes and may include a partial billing day, so the estimate is approximate.
Search: 4 shared CPUs, 2 GiB memory, 60 GB volume. Ingester: 1 shared CPU, 256 MiB. The measured spend includes volumes and backups.
Workers · usage-based estimate
The $5 Standard plan base is shared and is not assigned to Typeahead here. At this day's rate: 7.84M monthly invocations and 31.27M CPU ms. Against an otherwise unused paid allowance, CPU overage would be about $0.03; request usage stays below 10M.
This is a shared account: other Workers may consume the included usage. KV and observability charges still need attribution. Pricing and allowances.
engineering opportunities
Request accounting currently issues two logical SQL statements for a cached search and four for a successful origin search. Attribute those writes before replacing them with batched counters or Analytics Engine.
Measure export bytes per build and retry, retained index sizes, and overlay apply time. Rebuild frequency trades export cost against overlay size and search performance.
sources & assumptions
Cloudflare GraphQL analytics, Sep 4 23:00–Sep 5 23:00 UTC. Sampled estimates for all Worker routes, including ingestion. Hourly totals reconcile with the full-window query. Traffic and CPU projections multiply that window by 30; they are scenarios, not invoices.
CPU quantiles: P95 7.71 ms, P99 13.06 ms. Zero reported runtime errors. Invocation wall time includes background work and is not search response latency.
Cloudflare metric definitions · Fly cost explorer · Turso invoices