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
F14818690: D18965.id45492.diff
Tue, Jan 28, 3:08 AM
F14818687: D18965.id45487.diff
Tue, Jan 28, 3:08 AM
F14818685: D18965.id.diff
Tue, Jan 28, 3:08 AM
Unknown Object (File)
Mon, Jan 27, 5:06 AM
Unknown Object (File)
Sat, Jan 25, 3:06 PM
Unknown Object (File)
Fri, Jan 24, 11:27 PM
Unknown Object (File)
Fri, Jan 24, 11:27 PM
Unknown Object (File)
Fri, Jan 24, 11:27 PM
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