Page MenuHomePhabricator

Add a `--background` option to the `./bin/repository parents` workflow.
AbandonedPublic

Authored by joshuaspence on Jun 3 2014, 4:30 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Dec 12, 6:41 AM
Unknown Object (File)
Fri, Dec 6, 8:33 AM
Unknown Object (File)
Nov 26 2024, 9:03 AM
Unknown Object (File)
Nov 26 2024, 9:03 AM
Unknown Object (File)
Nov 26 2024, 9:03 AM
Unknown Object (File)
Nov 26 2024, 8:39 AM
Unknown Object (File)
Nov 19 2024, 6:03 AM
Unknown Object (File)
Nov 2 2024, 8:33 PM
Subscribers

Details

Summary

Fixes T5242. Add a --background option to the ./bin/repository parents workflow such that the heavy lifting will be handled by a PhabricatorWorker in the task queue.

Test Plan

Not yet tested.

Diff Detail

Repository
rP Phabricator
Branch
repo_parents-background
Lint
Lint Passed
Unit
Tests Skipped
Build Status
Buildable 824
Build 824: [Placeholder Plan] Wait for 30 Seconds

Event Timeline

joshuaspence retitled this revision from to Add a `--background` option to the `./bin/repository parents` workflow..
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence added a reviewer: epriestley.

Can we just batch all the queries instead? Instead of running the deletes/inserts inline, queue them into $delete_sql and $insert_sql, then execute them in chunks. And maybe even batch the selects. I'd guess that will make this run many hundreds of times faster, not require all the daemon complexity and overhead, and be better for everyone.

In D9359#7, @epriestley wrote:

Can we just batch all the queries instead? Instead of running the deletes/inserts inline, queue them into $delete_sql and $insert_sql, then execute them in chunks. And maybe even batch the selects. I'd guess that will make this run many hundreds of times faster, not require all the daemon complexity and overhead, and be better for everyone.

Yeah, you're probably right.