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

Investigate Reduced Memory Footprint with Memory-Mapped Files #145

Open
michaelahlers opened this issue Dec 12, 2021 · 0 comments
Open

Investigate Reduced Memory Footprint with Memory-Mapped Files #145

michaelahlers opened this issue Dec 12, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@michaelahlers
Copy link
Owner

Generated resources (from #123), when respective companion objects are used and loaded, might—as more datasets are added—start creating too large a footprint. Could copying generated datasets out of the classpath and accessing them with memory mapping help? Probably not, but maybe a useful idea later on.

See also:

@michaelahlers michaelahlers added the enhancement New feature or request label Dec 12, 2021
@michaelahlers michaelahlers self-assigned this Dec 12, 2021
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
None yet
Development

No branches or pull requests

1 participant