Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rule of thumb for when JLSO is inefficient in terms of file size #120

Closed
cossio opened this issue Feb 2, 2022 · 0 comments · Fixed by #121
Closed

Rule of thumb for when JLSO is inefficient in terms of file size #120

cossio opened this issue Feb 2, 2022 · 0 comments · Fixed by #121

Comments

@cossio
Copy link
Contributor

cossio commented Feb 2, 2022

Regarding this note from the Readme:

Note: If the amount of data you have to store is very small, relative to the metadata about your environment, then JLSO is a pretty suboptimal format.

I'd say it's not clear when JLSO is or is not efficient to store your data.
Perhaps this note can be extended, to clarify this explicitly:

Note: If the amount of data you have to store is very small, relative to the metadata about your environment, then JLSO is a pretty suboptimal format. As a rule of thumb, consider the size of your Project.toml and Manifest.toml files. If the data you are storing is large compared to the size (compressed) of these files, then it is fine to use JLSO.

If people agree I can do a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant