[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4067: Running the Tahoe CLI takes 400+ milliseconds just to start
Tahoe-LAFS
trac at tahoe-lafs.org
Mon Sep 25 15:07:52 UTC 2023
#4067: Running the Tahoe CLI takes 400+ milliseconds just to start
----------------------+----------------------------------------------
Reporter: itamarst | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Performance and Benchmarking
Component: unknown | Version: n/a
Keywords: | Launchpad Bug:
----------------------+----------------------------------------------
This may or may not be a priority, but basic `tahoe` commands take a while
to start. Profiling suggests this is just due to code imports.
The ~400ms is from a i7-12700k, so a very fast CPU core. A large
percentage of computers will be rather slower.
For many use cases this is OK. If you're doing heavy scripting with `tahoe
get' or something this will add up.
Potential solutions are:
* Something like PyOxidizer, which is designed to package up Python CLIs
in ways that make them start faster.
* Rewrite the CLI with a different, faster language?
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4067>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list