Page MenuHomePhabricator

Add a `bin/bulk export` CLI tool to make debugging and profiling large exports easier
ClosedPublic

Authored by epriestley on Jan 30 2018, 1:54 PM.
Tags
None
Referenced Files
F18733296: D18965.diff
Tue, Sep 30, 10:26 PM
F18702796: D18965.diff
Sun, Sep 28, 1:35 AM
F18695836: D18965.id.diff
Sat, Sep 27, 6:39 AM
F18524515: D18965.diff
Sat, Sep 6, 12:58 PM
F18427972: D18965.diff
Aug 31 2025, 12:46 AM
F18303011: D18965.id45492.diff
Aug 23 2025, 9:20 PM
F18224550: D18965.diff
Aug 20 2025, 12:09 AM
F17943812: D18965.id.diff
Jul 31 2025, 8:47 AM
Subscribers
None

Details

Summary

Ref T13049. When stuff executes asynchronously on the bulk workflow it can be hard to inspect directly, and/or a pain to test because you have to go through a bunch of steps to run it again.

Make future work here easier by making export triggerable from the CLI. This makes it easy to repeat, inspect with --trace, profile with --xprofile, etc.

Test Plan
  • Ran several invalid commands, got sensible error messages.
  • Ran some valid commands, got exported data.
  • Used --xprofile to look at the profile for a 300MB dump of 100K tasks which took about 40 seconds to export. Nothing jumped out as sketchy to me -- CustomField wrangling is a little slow but most of the time looked like it was being spent legitimately.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable