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
As evidenced in the recent profiling work I did on source-postgres (see #31298 (comment) ) a lot of the time is spent spinning up testcontainers.
The problem is multifold:
the tests are grouped and run in classes which represent a specific mode of operation for the connector (usually reflected in the form of different connector configs). This is sensible, but for good performance we need to group them in terms of which database resource they need.
some testcontainers (looking at you, ssh bastion and PostgresUtils.getCertificates) are effectively rebuilt from scratch every time and would be better off packaged as a docker image on Docker Hub as part of the CDK build.
The text was updated successfully, but these errors were encountered:
Topic
No response
Relevant information
As evidenced in the recent profiling work I did on source-postgres (see #31298 (comment) ) a lot of the time is spent spinning up testcontainers.
The problem is multifold:
PostgresUtils.getCertificates
) are effectively rebuilt from scratch every time and would be better off packaged as a docker image on Docker Hub as part of the CDK build.The text was updated successfully, but these errors were encountered: