WordCamp Europe 2018 Contributor Day Performance Changes #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
ataylorme
reviewed
Jul 9, 2018
performance/performance.md
Outdated
|
|
||
|  | ||
|
|
||
| > 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** |
There was a problem hiding this comment.
@getsource can we move this to an issue and get rid of inline TODO comments?
ataylorme
approved these changes
Jul 9, 2018
|
Fine with whenever you want to merge, or I can go ahead, so that there are fewer conflicts going forward. |
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.
This was referenced Aug 17, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.