Hello, i'm trying `kapt.classloaders.cache.size` option, and have really nice results: KaptWithout...

# kapt

[dsvoronin]

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

# 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?

[tapchicoma]

hmm, I would say number of annotation processors your project is using

[dsvoronin]

so it's a documentation flaw? it should say processors, not modules?

[dsvoronin]

https://youtrack.jetbrains.com/issue/KT-28901#focus=Comments-27-5183220.0-0
Also asked here

[Zac Sweers]

if you don't mine me asking - how did you measure those task totals? Something from kapt.verbose or gradle-specific?

[dsvoronin]

it's from build scan, timeline page

[tapchicoma]

I was wrong regarding my statement and answered in the issue regarding your question

[tapchicoma]

though I would leave it as 250, as cache should only grow up to unique kapt* configurations...

[dsvoronin]

Thanks, Yahor! I understood
think it is worth mentioning in docs if feature is here to stay

[tapchicoma]

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

[Dmytro Serdiuk]

Hello, @tapchicoma!

May I ask you two questions for the clarification:
• so the optimal cache size is equal to uniques kapt configs in all modules + small buffer?
• what is the purpose of “kapt.include.compile.classpath=false” for caching classloaders?
Thank you!