-
Notifications
You must be signed in to change notification settings - Fork 32
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
genext2fs is painfully slow for multi-GB input #31
Comments
Hi @josch, indeed I have some ideas to mitigate this; I'm currently a bit short on time but I may try something. |
The "easy" way is just to throw a big tarball at it. 😄 For example here is a big system image: https://mister-muffin.de/reform/target-userland-full.tar |
Any luck looking into this? I've hit this issue as well. For me with a ~10gb tar it seems to basically never complete (on a very powerful machine). |
Some quick benchmarks that I did make me think there is something highly nonlinear going on: note: these were done with a tar of a single file of the above sizes. |
I observed the same non-linear behavior. Since this is breaking my use-case for genext2fs I instead worked on a patch for e2fsprogs that would allow it to use a tarball as input: tytso/e2fsprogs#118 |
I'm trying to build a 8G image using |
Switched to |
@pamolloy did the local issue look something like this:
If yes, maybe try out #30 and tell me if that fixes your issue? As for the slowness, I do not know how to fix genext2fs but if you want tarball input, then maybe tytso/e2fsprogs#118 is of interest to you? |
Hi,
I'm now using genext2fs with multi-GB tarballs as input. While this works well it also takes several hours on my machine. So I profiled genext2fs:
gprof.txt
If I read the profiling output correctly, then most time is spent in the function
allocate()
.Do you have any ideas how to improve the speed by introducing better data structures?
The text was updated successfully, but these errors were encountered: