Page MenuHomePhabricator

When computing revision ownership, cache some intermediate results for performance
ClosedPublic

Authored by epriestley on Feb 27 2017, 4:05 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 16, 2:41 PM
Unknown Object (File)
Thu, Apr 11, 9:47 AM
Unknown Object (File)
Mon, Apr 8, 10:26 AM
Unknown Object (File)
Mon, Apr 1, 12:18 PM
Unknown Object (File)
Mar 19 2024, 6:08 PM
Unknown Object (File)
Mar 19 2024, 6:08 PM
Unknown Object (File)
Jan 26 2024, 8:52 AM
Unknown Object (File)
Jan 21 2024, 5:12 AM
Subscribers
None

Details

Summary

Ref T12319. With large datasets, the computation of which packages own paths in a revision is needlessly slow.

Improve performance through caching:

  • Cache which paths belong to each repository.
  • Cache the split fragments of each path.
  • Cache the path fragment counts.
  • Micro-optimize accessing $this->path.
Test Plan
  • Used bin/lipsum to generate 4,000 packages with 150,000 paths.
  • Created a revision affecting 100 paths in phabricator/ (these paths mostly overlap with bin/lipsum path rules, since Lipsum uses Phabricator-like rules to generate paths).
  • Before optimizations, this revision spent about 5.5 seconds computing paths.
  • After optimizations, it spends about 275ms.

Screen Shot 2017-02-27 at 8.01.39 AM.png (1×2 px, 375 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable