<p>To debug where the delay is, you can enable <a href="http://buildwithcraft.com/docs/config-settings#devMode" rel="nofollow">devMode</a>, which will write out a bunch of code and database profiling information to your log files in <code>craft/storage/runtime/logs</code>.</p>

<p>After you do that, save an entry then find that request in the log files.  You can look at the timestamps on that request to see what part of the code the 30 second delay is occurring on, which will point you in the direction of the underlying problem.</p>

CC BY-SA 3.0
2015-04-17T16:01:12.397Z
2015-04-17T16:01:12.397Z
Brad Bell
<p>I have a problem with the admin panel being very slow when saving an entry. It takes about 30 seconds to save an entry. I use a matrix for the different part of the entry (imgs, textfields, titles and so on). Does anyone else have this problem, and have someone found a solution for this? :)</p>

CC BY-SA 3.0
2015-04-17T13:07:31.133Z
I have one site hosted on Dreamhost and it does this and I can't figure out why. It's only for entries too. Globals seem to save fine.
Peter Tell
<entry><saving>
Saving entries in admin panel
# Saving entries in admin panel

(Asked by: username_0 on 2015-04-17)

I have a problem with the admin panel being very slow when saving an entry. It takes about 30 seconds to save an entry. I use a matrix for the different part of the entry (imgs, textfields, titles and so on). Does anyone else have this problem, and have someone found a solution for this? :)

**Tags:** entry, saving
> **Comments:**
> **username_1**: I have one site hosted on Dreamhost and it does this and I can't figure out why. It's only for entries too. Globals seem to save fine.  

---

## 1 answers

### Answer by username_2 on 2015-04-17. Score: 1

To debug where the delay is, you can enable [devMode](http://buildwithcraft.com/docs/config-settings#devMode), which will write out a bunch of code and database profiling information to your log files in `craft/storage/runtime/logs`.

After you do that, save an entry then find that request in the log files. You can look at the timestamps on that request to see what part of the code the 30 second delay is occurring on, which will point you in the direction of the underlying problem.


---

