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

Is it possible to guess the amount of memory RetDec will need for decompilation? #572

Closed
SamDecrock opened this issue May 15, 2019 · 2 comments

Comments

@SamDecrock
Copy link

Is there a way to guess the amount of memory retdec is going to need for decompilation?

I'm thinking of creating a web service to automate decompilation. The idea is to spin up a cloud instance with the right amount of memory, do decompilation and shut it down once decompilation is done.

To optimize costs (= decide which cloud instance to spin up) it would be good if I could know how much memory the process is going to take up.

Sam

@s3rvac s3rvac changed the title Guess the amount of memory up front Is it possible to guess the amount of memory RetDec will need for decompilation? May 15, 2019
@s3rvac
Copy link
Member

s3rvac commented May 15, 2019

Hi. I am afraid that there is no simple relation between static properties of the input file and the amount of memory RetDec will need to decompile it. A rule of thumb may be the bigger the file, the more memory RetDec may need, but this is generally an oversimplification. The amount of memory depends on many factors, including the number of instructions in the file, whether RetDec is able to correctly decode the instructions, detection of statically linked code, and decompilation parameters (e.g. selective decompilation may require less memory than full decompilation).

One of our long-term goals is to reduce memory requirements of RetDec (#13), but this is going to be a long run.

@s3rvac s3rvac closed this as completed May 15, 2019
@SamDecrock
Copy link
Author

SamDecrock commented May 15, 2019

Ok, I figured the "the bigger the file, the more memory RetDec may need" was going to be my only option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants