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

Cache symbolic filesystem when serialising the engine #84

Open
Boyan-MILANOV opened this issue Apr 9, 2022 · 0 comments
Open

Cache symbolic filesystem when serialising the engine #84

Boyan-MILANOV opened this issue Apr 9, 2022 · 0 comments
Assignees

Comments

@Boyan-MILANOV
Copy link
Collaborator

Currently when serialising FileSystem, we dump the entire symbolic filesystem. When the filesystem contains many shared library files it results in a lot of overhead when dumping/loading states.

Since many shared library files will likely only be read by the program, and never modified, we could gain a lot of time and storage by caching their contents in memory and avoid serialising them when possible.

The best solution will probably to implement a dynamic cache for env files that keeps track of the PhysicalFile internal buffers with a copy-on-write mechanism.

@Boyan-MILANOV Boyan-MILANOV self-assigned this Apr 9, 2022
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

No branches or pull requests

1 participant