![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
#60697 closed defect (bug) (fixed)
HTML API: Defer applying updates until necessary.
| Reported by: | dmsnell | Owned by: | audrasjb |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.5 |
| Component: | HTML API | Version: | 6.3 |
| Severity: | normal | Keywords: | has-patch has-unit-tests dev-reviewed fixed-major |
| Cc: | Focuses: |
Description
When making repeated updates to a document, the Tag Processor will end
up copying the entire document once for every update. This can lead to
catastrophic runtime behavior in the worse case.
However, when batch-applying updates it's able to copy chunks of the
document in one go and only end up copying the entire document once
for the entire batch.
Previously the Tag Processor has been eagerly applying updates, but in
this patch it defers applying those updates as long as is possible.
Change History (10)
This ticket was mentioned in PR #6120 on WordPress/wordpress-develop by @dmsnell.
2 years ago
#1
- Keywords has-patch has-unit-tests added
This ticket was mentioned in Slack in #core-performance by dmsnell. View the logs.
2 years ago
#3
@
2 years ago
- Version trunk → 6.3
Setting version to 6.3 because it was indicated on Slack that this might have been introduced in [55706].
#5
@
2 years ago
- Keywords dev-feedback added
- Milestone Awaiting Review → 6.5
- Resolution fixed
- Status closed → reopened
Re-opening for back-port to 6.5.
Trac ticket: Core-60697
When making repeated updates to a document, the Tag Processor will end
up copying the entire document once for every update. This can lead to
catastrophic behavior in the worse case.
However, when batch-applying updates it's able to copy chunks of the
document in one thread and only end up copying the entire document once
for the entire batch.
Previously the Tag Processor has been eagerly applying updates, but in
this patch it defers applying those updates as long as is possible.