Ross ROSS = Recommend OSS · open-source software intelligence for agents

ray-project/llm-numbers resource

Numbers every LLM developer should know observed · 2026-08-28

github.com/ray-project/llm-numbers observed · 2026-08-28

Health v2 · maintenance only

29/100

  • Activity 0
  • Release rhythm 35
  • Longevity 86

Flags: no_releases no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 1204
  • days_rel: n/a
  • days_push: 960
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

4315 stars · 140 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

A reference document listing key numbers and rules of thumb that LLM developers should know for back-of-the-envelope calculations, inspired by Jeff Dean's 'Numbers every Engineer should know'. It covers tokenization ratios, prompt cost savings, and price comparisons between LLM models and services.

Use cases

  • estimate token counts from word counts for LLM billing
  • compare costs between GPT-4 and GPT-3.5 Turbo for a task
  • decide when to use embeddings lookup versus text generation
  • learn how prompt phrasing like 'be concise' affects API costs
  • do quick back-of-the-envelope math for LLM application budgets
  • understand how context window sizes relate to document length

When to choose

  • you are new to LLM development and need intuition for token-based pricing
  • you want quick reference numbers for estimating LLM application costs
  • you are deciding between model tiers for one-off versus in-cycle tasks
  • you need a shared vocabulary of LLM cost facts for your team

When to avoid

  • you need up-to-date pricing since the document was last updated in 2023
  • you want runnable code or tooling rather than a reference document
  • you need vendor-neutral numbers beyond OpenAI, Anthropic, and Cohere examples
  • you require rigorous benchmarks rather than rules of thumb

Facets

learning-resource · maturity maintenance

llm-inference prompt-engineering developer-tools large-language-models tutorials developer-tools cross-platform reference-guide llm-cost-optimization back-of-envelope-calculations token-pricing documentation

1 source

Member repositories

RepositoryRoleHealth v2
ray-project/llm-numbersmain29

For agents

markdown · JSON · MCP: product_card(name="ray-project/llm-numbers")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem