WordPress / WordPress/performance
Improve handling of mega objects
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 461
- Forks
- 165
- Avg merge
- 11h 12m
- Merged PRs (30d)
- 28
Description
Extracted from #36.
The alloptions cache key can be several hundred megabytes and could use better handling. Some 3rd party plugins handle this by splitting it up. Can core do the same?
Instead of focussing only of the alloptions keys, maybe cache keys can be designated as MEGA and object cache implementations can handle them as they please.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the extracted issue #36 and tracing how the alloptions cache key is handled by core and object cache implementations. Compare the third-party splitting approach mentioned here and identify the design decisions needed for mega cache keys. Done means a clearly agreed core approach with defined behavior for affected object-cache implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100