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

Investigate lot of allocations and time required in JobRepository benchmarks #422

Open
sbchaos opened this issue Jun 23, 2022 · 0 comments

Comments

@sbchaos
Copy link
Contributor

sbchaos commented Jun 23, 2022

We have the following data from the JobRepository benchmarks:

BenchmarkJobRepository/Save-16           	       1	1375010724 ns/op	 3291376 B/op	   11338 allocs/op
BenchmarkJobRepository/GetByName-16      	       1	20054992147 ns/op	98418488 B/op	 1075058 allocs/op
BenchmarkJobRepository/GetAll-16         	       1	20741357727 ns/op	135020856 B/op	 1552099 allocs/op
BenchmarkProjectJobRepo/GetByName-16     	       1	19931592173 ns/op	98327032 B/op	 1074752 allocs/op
BenchmarkProjectJobRepo/GetAll-16        	       7	 160527678 ns/op	37056641 B/op	  478188 allocs/op

We should investigate the test and code to identify the source of too many allocations and add a fix for the same.

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

No branches or pull requests

2 participants