You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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.
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
The text was updated successfully, but these errors were encountered: