https://kotlinlang.org logo
#kapt
Title
# kapt
d

dsvoronin

09/02/2021, 9:33 PM
Hello, i'm trying
kapt.classloaders.cache.size
option, and have really nice results: KaptWithoutKotlincTask: Found 243 tasks executed in 243 projects totaling 6m 59.605s (without cache) Found 243 tasks executed in 243 projects totaling 2m 3.507s (with cache) my question: is 250 a sane number for cache.size option? it says
Copy code
# use the same value as the number of modules that use kapt
but something tells me that it might be an overkill, or it's ok?
t

tapchicoma

09/06/2021, 5:57 PM
hmm, I would say number of annotation processors your project is using
d

dsvoronin

09/07/2021, 3:34 PM
so it's a documentation flaw? it should say processors, not modules?
🤔 1
z

Zac Sweers

09/09/2021, 4:38 PM
if you don't mine me asking - how did you measure those task totals? Something from
kapt.verbose
or gradle-specific?
d

dsvoronin

09/09/2021, 6:53 PM
it's from build scan, timeline page
👍 1
t

tapchicoma

09/14/2021, 12:59 PM
I was wrong regarding my statement and answered in the issue regarding your question
though I would leave it as 250, as cache should only grow up to unique kapt* configurations...
👍 1
d

dsvoronin

09/14/2021, 4:19 PM
Thanks, Yahor! I understood think it is worth mentioning in docs if feature is here to stay
t

tapchicoma

09/14/2021, 6:33 PM
I think adding additional documentation will bring more confusion, then benefit - cache initial size is 16 and it will grow up to project unique kapt configurations. So current statement to set max size to be equal number of modules is fail safe and does not add overhead
👌 1
27 Views