# ARM Linux: CPU usage 99% for many hours with no progress on syncing

**URL:** https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-many-hours-with-no-progress-on-syncing/5322
**Category:** Support
**Created:** [August 4, 2015, 9:53pm UTC](https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-many-hours-with-no-progress-on-syncing/5322 "2015-08-04T21:53:32Z")
**Posts on this page:** 5
**Page:** 2

<div class="post-metadata">

### Author: ![ai91](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/a/ba9def/32.png) [@ai91](https://forum.syncthing.net/u/ai91)
#### Post date: [August 8, 2015, 1:28pm UTC](https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-many-hours-with-no-progress-on-syncing/5322/21 "2015-08-08T13:28:42Z")

</div>

> [@jorgen\_k](#):
>
> I changed the pingTimeoutS to 300 and the pingIdleTimeS to 600

@jorgen_k, where exactly did you change that? On ARM device only, or on all devices in the cloud?

---

<div class="post-metadata">

### Author: ![jorgen\_k](https://forum.syncthing.net/user_avatar/forum.syncthing.net/jorgen_k/32/1763_2.png) [@jorgen\_k](https://forum.syncthing.net/u/jorgen_k)
#### Post date: [August 8, 2015, 1:31pm UTC](https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-many-hours-with-no-progress-on-syncing/5322/22 "2015-08-08T13:31:56Z")

</div>

On all devices in my cluster.

I think it is like this, Machine A is slow. Machine B emits a ping to machine A, that times out. Machine B reconnects, and Machine A do a full rescan of everythinig. This starts over and over… I have no evidence, but changing the timeout on all members made it.

You change it easiest in the web gui, under _Advanced_ then _Options_, or by editing the config.xml.

---

<div class="post-metadata">

### Author: ![ai91](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/a/ba9def/32.png) [@ai91](https://forum.syncthing.net/u/ai91)
#### Post date: [August 9, 2015, 8:08am UTC](https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-many-hours-with-no-progress-on-syncing/5322/23 "2015-08-09T08:08:29Z")

</div>

> [@calmh](#):
>
> Leave it be, and don’t open the GUI, and it should complete the scan and be happy at some point.

Unfortunately bolt-build still can’t finish properly.

Started single ARM instance, with no other devices in cloud, no WebGUI, just indexing. Again got _fatal error: fault_. And boltdb size again = 2048Mb.

[panic-20150808-220817.log](https://forum-uploads.syncthingcdn.net/original/2X/7/798c0949800f69d2c3e117c8b3b9521da18543d0.log) (34.7 KB)

Switching to release on leveldb. Will try ‘isolated’ indexing on it.

---

<div class="post-metadata">

### Author: ![jangrewe](https://forum.syncthing.net/user_avatar/forum.syncthing.net/jangrewe/32/1501_2.png) [@jangrewe](https://forum.syncthing.net/u/jangrewe)
#### Post date: [August 9, 2015, 10:08am UTC](https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-many-hours-with-no-progress-on-syncing/5322/24 "2015-08-09T10:08:50Z")

</div>

I have the same NAS and had the same problems. Changing the timeouts helped a lot - in terms of actually syncing anything at all now! 😉

The CPU usage is still usually ~97% and it takes some time to catch up with the other boxes, but i’m using it as backup storage only, so it’s not all bad.

I think the initial sync took closer to a week than hours/days, even with most of the data already being on there (i used BT Sync before), so the hashing and DB I/O seems to be the main issue on that device.

(~400.000 files, 1.4TB)

---

<div class="post-metadata">

### Author: ![system](https://forum-uploads.syncthingcdn.net/original/2X/0/0b50e0a202b22ae6a67190759e8c868805b8ed9f.png) [@system](https://forum.syncthing.net/u/system)
#### Post date: [May 12, 2017, 12:59pm UTC](https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-many-hours-with-no-progress-on-syncing/5322/26 "2017-05-12T12:59:21Z")

</div>



[Previous page](https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-many-hours-with-no-progress-on-syncing/5322.md?page=1)