The analysis process is very slow about codyze

[fwendland]

Hi tiandiyixian,

Can you send me a link to the WebGoat5.0 project?

It's very difficult to give you useful advice without having some idea what your trying to analyze.

[JulianSchuette]

Hi tiandiyixian!

Neither Codyze nor CPG have been optimized for performance until now, so there is definitely room for improvement. Having said that, running the analysis all night without getting results sounds like a bug and if you provide the GitHub link, we will check what is wrong here.

We did a rough performance estimate on ~1400 Github projects. As you can see in the diagram, the majority of files (not projects) is well below 2 seconds, the median is somewhere 700ms-ish.

[tiandiyixian]

@fwendland
Hi fwendland ,
Thanks for your reply. This is my test case.:https://github.com/11112222/WebGoat5_0_32555lines/tree/master/WebGoat5.0. It ran for a long time when analyzing it, or the process was a memory leak and exit. After increasing the memory, it was a long wait.

[tiandiyixian]

@JulianSchuette
Thanks for your reply, maybe my test cases are special cases, webgoat 5.0 and OWASP benchmark, both of them have been analyzed for a long time without results, I will try other use cases

[JulianSchuette]

I am closing this since the upgrade to cpg 2.1.1 many things have changed and improved. However, there is still a bug (#32) in the deserialization module that needs to be fixed. When that is done, we will repeat the performance evaluation.