# Scaling ES indexing CPU usage
**URL:** https://discuss.elastic.co/t/scaling-es-indexing-cpu-usage/39979
**Category:** Elasticsearch
**Created:** [January 24, 2016, 9:40pm UTC](https://discuss.elastic.co/t/scaling-es-indexing-cpu-usage/39979 "2016-01-24T21:40:37Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@shaharmor](https://discuss.elastic.co/u/shaharmor)
#### Post date: [January 24, 2016, 9:40pm UTC](https://discuss.elastic.co/t/scaling-es-indexing-cpu-usage/39979/1 "2016-01-24T21:40:37Z")
Hey,
Is it possible to start ES servers that will help with indexing regarding CPU usage? And maybe just send the indexed data back to the server that is actually holding the shard itself?
Or if i try that it will just forward the request to the other server?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [January 24, 2016, 9:46pm UTC](https://discuss.elastic.co/t/scaling-es-indexing-cpu-usage/39979/2 "2016-01-24T21:46:42Z")
Data is sent to the node that has the appropriate shard.
The only way around this is to use hot/cold architecture, like so [https://www.elastic.co/blog/hot-warm-architecture](https://www.elastic.co/blog/hot-warm-architecture)
---
### Author:  [@shaharmor](https://discuss.elastic.co/u/shaharmor)
#### Post date: [January 24, 2016, 9:58pm UTC](https://discuss.elastic.co/t/scaling-es-indexing-cpu-usage/39979/3 "2016-01-24T21:58:54Z")
yeah thats what we're doing now but its not fast enough
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [January 24, 2016, 10:12pm UTC](https://discuss.elastic.co/t/scaling-es-indexing-cpu-usage/39979/4 "2016-01-24T22:12:51Z")
Then add more resources.
---
### Author:  [@klahnakoski](https://discuss.elastic.co/u/klahnakoski)
#### Post date: [January 25, 2016, 12:13am UTC](https://discuss.elastic.co/t/scaling-es-indexing-cpu-usage/39979/5 "2016-01-25T00:13:32Z")
It is my limited experience that the node with the primary shard does the cpu-intensive indexing work for that shard; the node with the most primary shards has the most CPU usage while indexing. Getting the primary shards to distribute evenly among all your machines is a challenge. I do use the hot/cold architecture: Specifically, my master nodes have no data. I only wish I did not have to learn it the hard way.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [January 25, 2016, 12:17am UTC](https://discuss.elastic.co/t/scaling-es-indexing-cpu-usage/39979/6 "2016-01-25T00:17:28Z")
> [@klahnakoski](#):
>
> the node with the most primary shards has the most CPU usage while indexing
Depends, do you have replicas? Because a replica does the same amount of work as a primary.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:22pm UTC](https://discuss.elastic.co/t/scaling-es-indexing-cpu-usage/39979/7 "2017-07-05T23:22:02Z")