Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate caching to Surge? #771

Open
iandunn opened this issue May 20, 2022 · 6 comments
Open

Migrate caching to Surge? #771

iandunn opened this issue May 20, 2022 · 6 comments

Comments

@iandunn
Copy link
Member

iandunn commented May 20, 2022

Our own @kovshenin released a lean caching plugin that looks really good. It'd be simpler and cleaner than WPSC, so I think we should consider migrating.

We could use nginx microcache if want to go even further, but that may not be worth it.

Any thoughts @ryelle @dd32 @coreymckrill?

@dd32
Copy link
Member

dd32 commented May 23, 2022

What's the intention behind it? Something simpler and with less options?

I'm unaware of any of the existing shortcomings or issues that the current plugin has though, so I tend to err on the side of don't touch it if it's working.

WordPress.org pretty much exclusively uses nginx caching, which doesn't have purge support, but is only for logged out users and short cache ttl's.

@kovshenin
Copy link
Contributor

Thanks for considering this! I'll be happy to help with the setup (there isn't much, really), and any custom configuration you might need, like invalidating things on certain custom events.

@iandunn
Copy link
Member Author

iandunn commented May 23, 2022

I tend to err on the side of don't touch it if it's working

Yeah, I think that's a good instinct in general.

What's the intention

The aren't any tangible problems at the moment, but in the past we've run into a few:

The simplicity of Surge is appealing as a way to minimize the chances of that stuff in the future, and to remove some of the customizations we've added with something that "just works".

It'd also give us caching for wp-json endpoints, and would be a devex improvement IMO.

There's always the chance that it could introduce new problems, though. The lack of preloading would probably be a performance hit, too. We could mitigate it to some extent w/ a longer TTL.

I think it'd be nice, but don't feel strongly.

@dd32
Copy link
Member

dd32 commented May 23, 2022

It'd also give us caching for wp-json endpoints, and would be a devex improvement IMO.

That alone would make it worth investigating IMHO. Especially given some current (and many future) things are likely built on top of it.

@timiwahalahti
Copy link
Collaborator

I always like simplifying things, so 👍 from me. Maybe we could roll Surge out in phases, starting tests with a small number of old WordCamp sites and gradually testing more with upcoming events before sunsetting WP Super Cache completely?

Let me know if there's anything I can help with these efforts :)

@iandunn
Copy link
Member Author

iandunn commented Sep 26, 2022

If we do this we should also grep the code for DONOTCACHEPAGE and other things specific to WPSC, and do them in a more plugin-agnostic way (like nocache headers).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants