Hi All,
I am a student from the University of Paderborn (Germany), who is curious about the debloating field and currently working on a Master’s thesis related to developing a Benchmarking tool for analyzing the Java Debloating tools.
I have used the Proguard tool and am impressed with its performance and ease of use. Therefore, I have decided to evaluate Proguard’s performance on our benchmark.
When using the tool I could see a lot of configuration settings available . It would be nice if you could guide us to configure your tool to effectively debloat the bloated parts while retaining the required components in the JAR. This guided configuration would help ensure that the tool operates at optimal efficiency and allows for a fair comparison with other tools.
The "Background of our Benchmarking Tool" section provides an introduction to our benchmarking tool. This information might help you assist in selecting the ideal configuration settings for my requirement.
Background of our Benchmarking tool:
We have developed a JAR file that consists of feature-wise test samples. This JAR file is used as a dependency in another JAR file. The final JAR is given as an input to the Debloating tool and the output JAR is used for our evaluation. In the evaluation, we will be checking whether the bloated elements (those are classes, methods and fields) are removed and whether the required elements are present in the debloated JAR by using the “name” of those elements.
Thanks in advance.