You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Several Tapis CLI commands appear take longer to run (or return a response) than their Bash analogues. See the table below. Times are in seconds and are the aggregate of 5 measurements.
Command
Tapis CLI
Bash CLI
apps-list -l 10
1.56+/-0.22
0.54+/-0.08
systems-list -l 10
1.42+/-0.05
0.45+/-0.13
jobs-list -l 10
2.03+/-0.05
0.95+/-0.09
metadata-list -l 10
1.33+/-0.07
0.43+/-0.09
The text was updated successfully, but these errors were encountered:
There are a couple of potential sources of overhead. First, Tapis CLI proactively refreshes its token on startup. Second, it is using the built-in Python JSON parser, which may be slower than either jq or the custom JSON parser written in Bash.
It should be possible to test the first possibility by passing a pre-created token via --token which bypasses the refresh. It might be possible to test the second by replacing the built-in JSON parser with a known more performant alternative.
Describe the bug
Several Tapis CLI commands appear take longer to run (or return a response) than their Bash analogues. See the table below. Times are in seconds and are the aggregate of 5 measurements.
apps-list -l 10
systems-list -l 10
jobs-list -l 10
metadata-list -l 10
The text was updated successfully, but these errors were encountered: