---
id: optimizations
title: Optimizations guides
meta:
    description: In this set of guides, you'll learn where to look when looking to optimize your Tinybird project, what to edit, and how to monitor changes.
---

# Optimizations

{% callout type="info" %}
This compilation of guides assumes some familiarity with using Tinybird (ingesting data, building query Pipes, publishing API Endpoints), particularly with using [Service Data Sources](/classic/monitoring/service-datasources).
{% /callout %}

The good news is that Tinybird is so fast that even for un-optimized projects, response times are excellent. Many projects, especially younger or smaller ones, won't necessarily or immediately *need* to optimize right now.

However, it's never too soon, especially because data moves fast. It's better to have 30ms latency than 300ms, and better to process less data so your [bills are smaller](/classic/pricing).

## About this section

The guides in this Optimizations section curate the best applied knowledge across Tinybird's docs ([Best practices for faster SQL](/classic/work-with-data/query/sql-best-practices)), videos ([Materialization process saves $40K](https://youtu.be/rfckIMbLWBg?si=dY1dP_ctx5tOSyhq), [Tips & Tricks to Keep Your Queries under 100ms](https://www.youtube.com/watch?v=MN2M6HAoO64)), blog posts ([Thinking in Tinybird](https://www.tinybird.co/blog-posts/thinking-in-tinybird)), and the deep expertise of our Data Engineering and Customer Support teams. It gives you both practical examples *and* a framework of questions you can ask in your own unique scenario. This combination should empower you with the tools, tips, tricks, and approach to build the best-optimized projects.

So, if you want to feel like [Marc](https://x.com/mfts0/status/1797651962692767801) or [Thibault](https://x.com/thibaultleouay/status/1699492486488498270), start digging in to the fascinating world of optimizing Tinybird projects.

## Optimizations mantra

Tinybird gives you the platform to manage your real-time data. Measure what matters, detect inefficiencies, fix and eliminate common (or unusual!) mistakes, and move faster. Remember, speed wins!

## Next steps

- Dive in with [Optimizations 101: Detecting inefficient resources](/classic/work-with-data/optimization/opt101-detect-inefficiencies).
- Improve the efficiency of project with [Optimizations 201: Fixing common mistakes](/classic/work-with-data/optimization/opt201-fix-mistakes).