# Cloudflare setup and other post-migration tasks

**URL:** <https://meta.discourse.org/t/cloudflare-setup-and-other-post-migration-tasks/252557>\
**Category:** Migration\
**Created:** [January 22, 2023, 9:41pm UTC](https://meta.discourse.org/t/cloudflare-setup-and-other-post-migration-tasks/252557 "2023-01-22T21:41:09Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Crius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crius/32/317214_2.png) [@Crius](https://meta.discourse.org/u/Crius)\
**Post date:** [January 26, 2023, 9:13am UTC](https://meta.discourse.org/t/cloudflare-setup-and-other-post-migration-tasks/252557/12 "2023-01-26T09:13:04Z")

</div>

Sorry for the delay in replies.

I don’t know enough about Discourse design but thinking about the presence of redis already manage some caching of common requests. That explain the “cloudflare not being really needed”

So, am I understanding it right as basically there is little to no benefit in having Cloudflare in front of a Discourse installation, and on the contrary, it would slow down response instead (network hops)?

The only reason for cloudflare for the vbulletin3 installation was that the amount of request would overwhelm the server and (just assuming here) could be because of the poor work in the code design of vbulletin3 to be honest because the VM that host it is a 4vcore, 8gb ram just for the application itself and another VM of equal specs for the DB.

There is no way any modern web-app need that much power today.

Speaking of, is there any reference I can consult to evaluate how much hw I would need for a discourse installation that on average have ~1K active users and ~5-6K lurkers?

---

_[View the full topic](https://meta.discourse.org/t/cloudflare-setup-and-other-post-migration-tasks/252557)._