# Component Back Pressure Behavior

When downstream components slow down, back pressure propagates upstream with each component slowing its intake to match. This is how pipelines avoid dropping data.

Components that buffer internally break this chain. When their internal buffers fill, they drop data silently with no signal to slow down upstream. This is especially dangerous with UDP sources.

#### Components That Break Back Pressure

These components buffer data internally and could silently drop data under load.

**Connectors**

| Name            | Mechanism                                                          |
| --------------- | ------------------------------------------------------------------ |
| Span to Metrics | Caches span data, flushes derived metrics on interval (default 5s) |

**Processors**

| Name                      | Mechanism                                                                                                                                                                                                                                                          |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Batch                     | Buffers telemetry, sends on size threshold (8192) or timer (200ms). No upper bound by default (`send_batch_max_size: 0`); set this to cap memory growth under sustained load.                                                                                      |
| Deduplicate Logs          | Holds logs in memory over time window (default 10s). Memory scales with unique log bodies, so high-cardinality logs defeat dedup and can cause unbounded memory growth under load. Held logs are lost on restart, and the deduplicated aggregate is never emitted. |
| Count Telemetry           | Accumulates counters, emits on interval (default 60s). Up to one full window of counts is lost on restart or crash.                                                                                                                                                |
| Compute Metric Statistics | Accumulates data over interval (default 60s). Up to one full window of statistics is lost on restart or crash.                                                                                                                                                     |

All other processors and connectors are synchronous; they process inline and maintain back pressure.

#### Placement Guidelines

* **Filter early.** Reduce volume before async components to minimize buffer pressure.
* **For UDP sources**, ensure sufficient upstream buffering or accept potential drops during spikes.
* **For high-volume pipelines** (100k+ events/sec), consider a gateway architecture for durable buffering. [See more.](https://docs.bindplane.com/production-checklist/bindplane-otel-collector/agents-v.-gateways)
* **Configure destination queuing** to match your durability requirements. [See more.](https://docs.bindplane.com/configuration/bindplane-otel-collector/persistent-queue)

For throughput and latency impact of processors, see [Processor Impact on Collector Performance.](https://docs.bindplane.com/feature-guides/processor-impact-on-agent-performance)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bindplane.com/feature-guides/pipeline-processing/component-back-pressure-behavior.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.