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

Add benchmark modules #14

Merged
merged 2 commits into from
Apr 6, 2024
Merged

Add benchmark modules #14

merged 2 commits into from
Apr 6, 2024

Conversation

anthonycr
Copy link
Owner

Created 2 modules with benchmarks for mockk and mockingbird, benchmark-mockingbird and benchmark-mockk as the control benchmark.

Currently, mockingbird benchmark runs using gradle-profiler for an average of 3610ms, while mockk runs with an average of 3263ms. This discrepancy is due to the lack of any KSP code generation running on the mockk benchmark. I did some preliminary testing, and it showed that if a KSP is added to the mockk, for example, if dagger is added to both benchmarks, the discrepancy is non existent and mockingbird performs slightly better. I'm going to leave the benchmarks without this for now.

In order to run the benchmarks, select a folder that you want to run the benchmark in, and then run

 gradle-profiler --benchmark --project-dir /Path/To/Mockingbird clean :benchmark-mockk:test

and

 gradle-profiler --benchmark --project-dir /Path/To/Mockingbird clean :benchmark-mockingbird:test

@anthonycr anthonycr added the enhancement New feature or request label Apr 6, 2024
@anthonycr
Copy link
Owner Author

See also #2

@anthonycr anthonycr merged commit ef42771 into main Apr 6, 2024
1 check passed
@anthonycr anthonycr deleted the benchmark branch April 6, 2024 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant