# Speed of refresh after editing a post

**URL:** https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725
**Category:** Support
**Created:** [January 28, 2019, 2:19pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725 "2019-01-28T14:19:35Z")
**Posts on this page:** 15
**Page:** 1

<div class="post-metadata">

### Author: ![adamengst](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/adamengst/32/116607_2.png) [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [January 28, 2019, 2:19pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/1 "2019-01-28T14:19:35Z")

</div>

One of my users says that it feels as though Discourse takes longer to refresh a post after it has been edited than it used to. I looked for settings related to this, but couldn’t find any. In my testing, posts update between 10 and 15 seconds after the edit is saved, which does seem to be rather slow. Why not update the post immediately after the user finished editing?

And just for giggles, I’ll see if this site updates differently from mine. Yes, it does—refreshes seem immediate here. So the question is, what could be different between the sites?

---

<div class="post-metadata">

### Author: ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)
#### Post date: [January 28, 2019, 2:55pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/2 "2019-01-28T14:55:48Z")

</div>

Yeah it should be pretty much immediate, **except** when your sidekiq queues are full or if your server is severely under dimensioned.

My starting point would be:

- Check the load of your server.
- Check the latency if your queues in Sidekiq → Queues

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 28, 2019, 3:16pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/3 "2019-01-28T15:16:54Z")

</div>

If you recently updated after a couple months then you’re discourse is likely processing all of your images. @bartv’s advice will show you if that’s the problem. There is a setting “rebake old posts count” that defaults to 80; you should likely change it to 20.

---

<div class="post-metadata">

### Author: ![adamengst](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/adamengst/32/116607_2.png) [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [January 28, 2019, 8:18pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/4 "2019-01-28T20:18:39Z")

</div>

Thanks, guys. We’re running at Digital Ocean, and it doesn’t seem like there are any CPU or memory issues.

 ![DigitalOcean-graphs](https://global.discourse-cdn.com/meta/original/3X/f/e/feec3e90d3944b80d9c5ff34c528b19fff2a20d4.png)

And similarly, the Sidekiq graphs don’t seem to show anything amiss:

 ![Sidekiq-queues](https://global.discourse-cdn.com/meta/original/3X/9/1/9130a1872226109a4e07d97cb0c0a89719d94dbe.png)

 ![Sidekiq-data](https://global.discourse-cdn.com/meta/original/3X/8/f/8f1731dd9a6e720a3110e92acc1d817d817f4da9.png)

Other thoughts? Thanks!

---

<div class="post-metadata">

### Author: ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)
#### Post date: [January 28, 2019, 8:27pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/5 "2019-01-28T20:27:10Z")

</div>

Are you on CloudFlare? Are you sure you disabled all their JS compression features?

---

<div class="post-metadata">

### Author: ![adamengst](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/adamengst/32/116607_2.png) [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [January 28, 2019, 8:42pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/6 "2019-01-28T20:42:49Z")

</div>

We are on Cloudflare, and we did have JavaScript enabled in their Auto Minify feature. I’ve turned it off and purge the cache and we’ll see if it makes a difference (or if we need it for other stuff). Are there other places Cloudflare compresses JavaScript?

---

<div class="post-metadata">

### Author: ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)
#### Post date: [January 28, 2019, 8:46pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/7 "2019-01-28T20:46:46Z")

</div>

Yeah, make sure Rocket Loader is switched off too.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [January 28, 2019, 9:11pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/8 "2019-01-28T21:11:07Z")

</div>

Don’t turn them off domain-wide, do this with a rule:

 ![](https://global.discourse-cdn.com/meta/original/3X/a/6/a6c869b853fb2765a8fd9d6df72b939b4d284d72.png)

Minification, Rocket Loader, Mirage and Polish should all be disabled. ‘Disable Performance’ achieves this.

Brotli compression is also unnecessary and has previously caused issues, it can be disabled at domain-level in the ‘speed’ section of the dashboard.

The only area where Cloudflare can really assist Discourse is with asste caching, feel free to create a secondary rule which enables cache level ‘Standard’ on /uploads/\* if you don’t employ some other form of CDN.

---

<div class="post-metadata">

### Author: ![adamengst](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/adamengst/32/116607_2.png) [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [February 13, 2019, 6:52pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/9 "2019-02-13T18:52:36Z")

</div>

Turns out the real culprit was CloudFlare’s Brotli https compression. The Auto Minify JavaScript didn’t make a difference.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [February 13, 2019, 6:54pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/10 "2019-02-13T18:54:18Z")

</div>

You need a page rule as follows:

 ![](https://global.discourse-cdn.com/meta/original/3X/1/3/13bc9663ffd3e069a6b6fb91a888ecc72a9b932b.png)

None of the ‘Performance’ features are supported with Discourse, Javascript minification has also caused issues in the past.

CloudFlare is ok as a CDN, but it’s also going to add unavoidable latency between client and server.

---

<div class="post-metadata">

### Author: ![adamengst](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/adamengst/32/116607_2.png) [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [February 13, 2019, 6:57pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/11 "2019-02-13T18:57:33Z")

</div>

Yeah, unfortunately, we’re at our limit for free page rules, so it’s hard to justify paying monthly for something that I can just tweak around in a slightly less elegant way. If we ever start paying for CloudFlare, I’ll definitely add this rule.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [February 13, 2019, 6:58pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/12 "2019-02-13T18:58:35Z")

</div>

Ok, well just be aware that the next time you ask for support it’s the first thing we’re going to need for you to do. We can’t support installs running unsupported configurations.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [February 13, 2019, 7:44pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/13 "2019-02-13T19:44:29Z")

</div>

> [@adamengst](#):
>
> Yeah, unfortunately, we’re at our limit for free page rules

You can make the orange cloud in the DNS entry for Discourse gray. That solves everything.

---

<div class="post-metadata">

### Author: ![adamengst](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/adamengst/32/116607_2.png) [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [February 13, 2019, 8:07pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/14 "2019-02-13T20:07:20Z")

</div>

Doh! Of course—good idea, and I’ll give that a try now.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [March 6, 2022, 4:17pm UTC](https://meta.discourse.org/t/speed-of-refresh-after-editing-a-post/107725/15 "2022-03-06T16:17:55Z")

</div>


