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.

Sign up for GitHub

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

Jump to bottom

memory usage during "applying strategy" is massive, maybe leaking #23

Open
jokeyrhyme opened this issue Sep 18, 2014 · 1 comment
Open

memory usage during "applying strategy" is massive, maybe leaking #23

jokeyrhyme opened this issue Sep 18, 2014 · 1 comment
Labels
bug
Milestone
1.0.0

Comments

@jokeyrhyme
Copy link
Owner

A source directory with ~7000 files totalling ~150MB seems to use over 3.5GB of RAM during the "applying..." phase.
@jokeyrhyme jokeyrhyme added the bug label Sep 18, 2014
@jokeyrhyme jokeyrhyme added this to the 1.0.0 milestone Dec 1, 2014
@jokeyrhyme
Copy link
Owner Author

Approach for scanning local files needs to change. Rather than scanning them all in advance, it may be a better bet to scan each one individually on-demand instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@jokeyrhyme