You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My recent investigations in profiling the performance of a source-postgres spec call in #31298 revealed that having less jars on the classpath might speed up the JVM startup and class initialization latency slightly.
The principal source of bloat is the CDK which just includes dependencies for everything. This was a fine choice for the purpose of getting the CDK out of the door in the first place but now we should improve things.
It also makes no sense for the source-postgres base image to weigh in at half a GB, this bloat has repercussions elsewhere as well (the build is slower, it just looks bad, etc.)
The text was updated successfully, but these errors were encountered:
Topic
No response
Relevant information
My recent investigations in profiling the performance of a source-postgres
spec
call in #31298 revealed that having less jars on the classpath might speed up the JVM startup and class initialization latency slightly.The principal source of bloat is the CDK which just includes dependencies for everything. This was a fine choice for the purpose of getting the CDK out of the door in the first place but now we should improve things.
It also makes no sense for the source-postgres base image to weigh in at half a GB, this bloat has repercussions elsewhere as well (the build is slower, it just looks bad, etc.)
The text was updated successfully, but these errors were encountered: