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
Currently, JSON minification is opt-in with the --minify-json option. However, it is not uncommon for large-scale analyses to have thousands of tips resulting in a dataset file that takes significantly more time to load compared to a minified version.
Other discussions and emails from users that have been affected by large Auspice JSONs
Proposed solution
Make JSON minification the default behavior for anything >1000 tips (threshold used by @trvrb's example on Slack). This allows smaller JSONs (which don't gain much performance benefit with minification) to be in the indented, human-readable format.
The text was updated successfully, but these errors were encountered:
I support minification by default. Should we offer an option for pretty printing or is that unnecessary as one can simply use jq '.' or similar to do so?
@corneliusroemer Yeah, that would be the (new) --no-minify-json option to disable minification (i.e. the current default behaviour). Discussed in the linked Slack thread, but not noted here.
proposed by @tsibley on Slack
Context
Currently, JSON minification is opt-in with the
--minify-json
option. However, it is not uncommon for large-scale analyses to have thousands of tips resulting in a dataset file that takes significantly more time to load compared to a minified version.Related issues
Proposed solution
Make JSON minification the default behavior for anything >1000 tips (threshold used by @trvrb's example on Slack). This allows smaller JSONs (which don't gain much performance benefit with minification) to be in the indented, human-readable format.
The text was updated successfully, but these errors were encountered: