Performance tuning of custom source connector

On comparing the custom source-connector http API with a regular python request call, we see there is a considerable time gap between the two. We have prepared below a chart to depict the time taken to pull the data using the airbyte custom connector vs without airbyte. Both of these are hosted on aws.
As shown in below table on an average the airbyte code is takes 4 times more time.

Could you please share some advice on why such a large added time and any ways to optimize.

with airbyte with airbyte with airbyte without airbyte without airbyte without airbyte
material 1371ms 1558ms 1282ms 379ms 398ms 388ms
vendor 1751ms 1773ms 1224ms 343ms 380ms 352ms

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

Hello, Pravesh!

Our team does not have the capacity or resources to support custom development questions right now, but I’d be happy to review the PR when you submit it! I hope someone from the community chimes in, also feel free to reach out to other community members who have contributed PRs!