# Indexing to Multiple Endpoints
**URL:** https://discuss.elastic.co/t/indexing-to-multiple-endpoints/250166
**Category:** Logstash
**Created:** [September 28, 2020, 10:45am UTC](https://discuss.elastic.co/t/indexing-to-multiple-endpoints/250166 "2020-09-28T10:45:01Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@dawiro](https://discuss.elastic.co/u/dawiro)
#### Post date: [September 28, 2020, 10:45am UTC](https://discuss.elastic.co/t/indexing-to-multiple-endpoints/250166/1 "2020-09-28T10:45:02Z")
Hi,
In a single pipeline scenario, how much of a performance cost is there to having more than one output configured? Will all outputs run at the speed of the slowest?
Thx
D
---
### Author:  [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [September 28, 2020, 12:28pm UTC](https://discuss.elastic.co/t/indexing-to-multiple-endpoints/250166/2 "2020-09-28T12:28:33Z")
> [@dawiro](#):
>
> Will all outputs run at the speed of the slowest?
If logstash is configured to write events to more than one output then if one of them slows down this can result in back pressure that eventually stop ingestion of events, so in the long run, yes, they will.
Using pipeline to pipeline communication with an [output isolator](https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.html#output-isolator-pattern) pattern can help with this.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 26, 2020, 12:28pm UTC](https://discuss.elastic.co/t/indexing-to-multiple-endpoints/250166/3 "2020-10-26T12:28:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.