<p>I'm running Craft on our shared hosting with PHP 7.2. No SSD. Performance is fine, but working in the backend, I often get hickups of several seconds (!), where nothing happens, everything stalls.</p>

<p>Here's what cPanels resources diagram tells us:</p>

<p><a href="https://i.sstatic.net/5cK7w.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/5cK7w.png" alt="enter image description here"></a></p>

<p>So ... something with I/O and I/O Faults.</p>

<p>Could this be solved without changing the hosting?</p>

CC BY-SA 4.0
2018-08-24T22:52:47.543Z
Having you tried contacting your host to let them know what you're seeing? Shared hosting is tricky because you're contenting for resources (including disk I/O) with every other site that is hosted on that box.
Brad Bell
CC BY-SA 4.0
2018-08-25T07:01:49.267Z
Is the I/O thing a particularity of twig, yii, craft? Does it write a lot of files?
Urs
CC BY-SA 4.0
2018-08-28T05:45:14.033Z
Not really?  99% of Craft's/Twig's writing on any given request will be in `craft/storage/runtime`.
Brad Bell
CC BY-SA 4.0
2018-09-03T11:34:41.197Z
Since the hoster raised the I/O limits, it's been going well. Still testing, but it looks like 2MB/s are required to avoid these timeouts
Urs
<performance><hosting>
Craft on a cPanel hosting with CentOS and CloudLinux – I/O faults?
# Craft on a cPanel hosting with CentOS and CloudLinux – I/O faults?

(Asked by: username_0 on 2018-08-24)

I'm running Craft on our shared hosting with PHP 7.2. No SSD. Performance is fine, but working in the backend, I often get hickups of several seconds (!), where nothing happens, everything stalls.

Here's what cPanels resources diagram tells us:

[![enter image description here](https://i.sstatic.net/5cK7w.png)](https://i.sstatic.net/5cK7w.png)

So ... something with I/O and I/O Faults.

Could this be solved without changing the hosting?

**Tags:** performance, hosting
> **Comments:**
> **username_1**: Having you tried contacting your host to let them know what you're seeing? Shared hosting is tricky because you're contenting for resources (including disk I/O) with every other site that is hosted on that box.  
> **username_0**: Is the I/O thing a particularity of twig, yii, craft? Does it write a lot of files?  
> **username_1**: Not really?  99% of Craft's/Twig's writing on any given request will be in `craft/storage/runtime`.  
> **username_0**: Since the hoster raised the I/O limits, it's been going well. Still testing, but it looks like 2MB/s are required to avoid these timeouts  

---

## 0 answers

