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

Caching of file extraction step #74

Open
ronaldtse opened this issue Feb 15, 2022 · 2 comments
Open

Caching of file extraction step #74

ronaldtse opened this issue Feb 15, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@ronaldtse
Copy link
Contributor

ronaldtse commented Feb 15, 2022

On every run, a tebako-compiled executable extracts the DwarFS image out into a temporary directory for execution.

We should cache this extraction step across runs, so we only extract the files when we need to:

  • e.g. a file is gone/corrupt, or the DwarFS image changed
@ronaldtse ronaldtse changed the title ㅊㅁ초ㅑㅜㅎ ㅐ Caching of file extraction step Feb 15, 2022
@ronaldtse ronaldtse added the enhancement New feature or request label Feb 15, 2022
@maxirmx
Copy link
Member

maxirmx commented Sep 9, 2022

tebako-compiled executable DOES NOT EXTRACT the DwarFS image out into a temporary directory for execution
It extracts some files that are directly accessed by Ruby extensions as expained here: #42 (comment)

If we want just extract the image we do not need DwarFS. Now we are following ruby-packer approcach and run the application from in-memory DwarFS filesystem.
Otherwise we could just compress ruby folder and extract it on startup just as OCRA does.

@ronaldtse
Copy link
Contributor Author

This issue applies to the part that is extracted, not the part that is accessible via DwarFS:

It extracts some files that are directly accessed by Ruby extensions

For the extracted part, we want the ability to cache/persist across calls if possible (eg at a persistent cache location).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🔖 Ready
Development

No branches or pull requests

2 participants