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 part of the investigation into speeding up check connection, our testing found that the check connection method (and discover schema method) for some connectors is slow (even after removing platform overhead)
Ideally, our 99 percentile for performing check connection is < 10 seconds. Given that the Kube overhead is ~5 seconds, we want the connector to finish in something like 3 seconds. This gives us 2 seconds of buffer to play with.
Results (does not include platform overhead):
destination Postgres - ~ 4 seconds (I was using this as a generic RDS connector)
I have tested 'check' and 'discover' methods via UI and CLI and I have not seen any significant delays ( about 1s)
I have also checked connector code and I have not seen any places where the problem can happen
I have reviewed related issues and spreadsheets and I actually was not able to find any evidence (and numbers) which could indicate slowness of check and discover methods.
@misteryeo, @davinchia is it enough to close this issue? or could you help me to find more information about circumstances in which I can re-produce the problem?
Relates to: #10149
Tell us about the problem you're trying to solve
As part of the investigation into speeding up check connection, our testing found that the check connection method (and discover schema method) for some connectors is slow (even after removing platform overhead)
Ideally, our 99 percentile for performing check connection is < 10 seconds. Given that the Kube overhead is ~5 seconds, we want the connector to finish in something like 3 seconds. This gives us 2 seconds of buffer to play with.
Results (does not include platform overhead):
Acceptance Criteria
If it is necessary to remove some thoroughness in the check connection (i.e: do fewer operations and get a less granular failure message)
The text was updated successfully, but these errors were encountered: