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

WordCamp Europe 2018 Contributor Day Performance Changes #35

Merged
merged 3 commits into from Aug 17, 2018

Conversation

Projects
None yet
3 participants
@getsource
Collaborator

getsource commented Jun 28, 2018

Includes contributions from jstrotmann, junglewp, crixu, jlsoft, juergenleber, hristo-sg and jadonn.

This is a lot of changes, so open for modifications or suggestions, but wanted to get it in a pull request as soon as it was possible.

WordCamp Europe 2018 Contributor Day Performance Changes
Includes contributions from jstrotmann, junglewp, crixu, jlsoft, juergenleber, hristo-sg and jadonn.

This is a lot of changes, so open for modifications or suggestions, but wanted to get it in a pull request as soon as it was possible.
![WordPress Object Caching Diagram](/assets/wordpress-object-caching-example.png)
> Transients are inherently sped up by caching plugins, where normal Options are not. A memcached plugin, for example, would make WordPress store transient values in fast memory instead of in the database. For this reason, transients should be used to store any data that is expected to expire, or which can expire at any time. Transients should also never be assumed to be in the database, since they may not be stored there at all.
###### source: [WordPress Codex](https://codex.wordpress.org/Transients_API)
A good example is a social media widget. A plugin may call out to a third-party API to fetch the latest social content. Rather than doing this on every page load the results can be stored in a transient. WordPress will store transients, these forms of expiring options, in the datbase. In most cases fetching the latest social posts from the database is faster than calling out to the social media API but object caching can improve this further. Rather than store those items in the database WordPress will make use of the persistent object cache, usually a fast memory store.
**TODO: Consider talking about autoload and Memcached**

This comment has been minimized.

@ataylorme

ataylorme Jul 9, 2018

Owner

@getsource can we move this to an issue and get rid of inline TODO comments?

This comment has been minimized.

@getsource

This comment has been minimized.

Collaborator

getsource commented Jul 27, 2018

Fine with whenever you want to merge, or I can go ahead, so that there are fewer conflicts going forward.

ataylorme and others added some commits Aug 17, 2018

Edit Pass.
General editing review. 

Larger changes of note:
* Removed Percona Stub. We might want to create a new issue to discuss if it's important to talk about performance with regards to Percona.
* Removed the included values for upload limits, because they showed PHP defaults, which in many cases are too low for production, but I'm unsure if we want to make a suggestion as to a specific setting or not. This could also use an issue for discussion, since I think having the samples is helpful.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment