https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
e

elihart

06/28/2021, 6:41 PM
The alpha release blog post says
using KAPT and KSP in the same module will likely slow down your build initially
- however, we did some gradle profiling of our own project with KSP enabled and found that mixing KSP/KAPT actually is slightly faster than using only KAPT (if not all processors support KSP) I’m wondering if there is any more current information about mixing KAPT and KSP in the same module (since alpha release was a while ago), and I’m curious to hear about other people’s experience
z

Zac Sweers

06/28/2021, 6:54 PM
what processors are running in each case?
j

Jiaxiang

06/28/2021, 6:54 PM
Thanks for doing the profiling. The reason we think there is going to be a slow down is because KAPT takes a long time and the best case for mixing is KSP taking minimal time which is still adding extra time to total build. It’s quite interesting to see it’s actually faster though.
t

Tyler Hodgkins

06/28/2021, 8:07 PM
I would assume this would be true in cases where the runtime of the processor itself is larger than the initialization time, assuming KSP performs better than KAPT in general.
j

Jiaxiang

06/28/2021, 8:09 PM
oh, if by mixing means replacing some KAPT processors with KSP processors, then it might be true if the KSP implementation of the processor is faster.
like leveraging the Sequence can definitely help with performance if used properly
y

yigit

06/28/2021, 8:52 PM
Wow this is very surprising, it could only be explained if the KSP is so much faster than javaP (which would be great:) ). I've not profiled running KSP and KAPT together. Also room's abstraction cannot benefit from some of the sequence benefits because of a bug in kotlin compiler where it does not report the declarations in the source order
e

elihart

06/28/2021, 10:05 PM
oh, if by mixing means replacing some KAPT processors with KSP processors, then it might be true if the KSP implementation of the processor is faster.
yes, this is what I mean. For example we have two processors in a module and only one supports KSP, we can either run both with KAPT or run one with KAPT and the other with KSP.
what processors are running in each case?
they’re in house processors
I am a little concerned about mixing processors backends in case processors rely on generated sources, but I suppose if it compiles for us it should be fine
j

Jiaxiang

06/28/2021, 10:07 PM
one thing will not work is if one processor is depending on another processor’s generated code.
e

elihart

06/28/2021, 10:10 PM
is that true in both directions (KSP processor relying on code gen from KAPT, or vice versa)? is there any sort of guarantee about which of KSP or KAPT runs first?
j

Jiaxiang

06/28/2021, 10:11 PM
I don’t think there is a guarantee on the order @Ting-Yuan Huang can you confirm on this?
t

Ting-Yuan Huang

06/28/2021, 10:17 PM
KSP and KAPT processors don't see generated sources from each other. There is no order guarantee.
Re: performance difference beyond stub generation: I got 2 conjectures. 1. In KAPT, the delegation to javac still builds the full AST and I guess it resolves everything. Although resolution in Java is considerably faster than Kotlin, it still takes time. If a KSP processor only focus on a small part of a large code base, it can be faster. 2. kotlinc reads libraries mainly from metadata, which is much more concise than bytecode. We suspect that this implementation is faster than javac which reads bytecode. So it can be faster if a processor processes a lot of libraries. If you're using incremental processing, KSP tracks dependencies dynamically while KAPT assumes the worst case. This can be a big difference. Though that currently KSP doesn't track inter-module dependencies (and always reprocess all) while KAPT does. For inter-module changes, KAPT has an edge for now.
👌🏼 1
e

elihart

06/28/2021, 11:13 PM
Thanks for all the info, that’s great to know! We only profiled clean builds, but your first theory makes sense because it is a very lean processor that operates only on a small percentage of files within our modules
👍 1