Page MenuHomePhabricator

Improve Remarkup parsing performance for certain large input blocks
ClosedPublic

Authored by epriestley on Feb 4 2020, 10:37 PM.
Tags
None
Referenced Files
F18784620: D20968.diff
Mon, Oct 13, 1:38 PM
F18736271: D20968.id.diff
Wed, Oct 1, 5:19 AM
F18734140: D20968.id.diff
Tue, Sep 30, 10:48 PM
F18725274: D20968.diff
Tue, Sep 30, 4:58 AM
F18654309: D20968.id.diff
Sep 22 2025, 6:00 AM
F18598552: D20968.id49962.diff
Sep 13 2025, 5:16 AM
F18567615: D20968.id.diff
Sep 9 2025, 3:58 PM
F18431454: D20968.id.diff
Aug 31 2025, 5:15 AM
Subscribers
None

Details

Summary

Fixes T13487. In PHI1628, an install has a 4MB remarkup corpus which takes a long time to render. This is broadly expected, but a few reasonable improvements fell out of running it through the profiler.

Test Plan
  • Saw local cold-cache end-to-end rendering time drop from 12s to 4s for the highly secret input corpus.
  • Verified output has the same hashes before/after.
  • Ran all remarkup unit tests.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

src/infrastructure/markup/remarkup/PhutilRemarkupEngine.php
250–254

This piece was pretty wild. It meant "Are both blocks default blocks (plain old paragraphs)?" but tested that in a very convoluted way.

This revision was not accepted when it landed; it landed in state Needs Review.Feb 4 2020, 11:07 PM
This revision was automatically updated to reflect the committed changes.