How memory request and limit works under the hood


I am trying to understand how airbyte deal with memory. Every time a conector reads a lot of records, I need to increase the vm memory and cpu. I found the JOB_MAIN_CONTAINER_MEMORY_REQUEST and JOB_MAIN_CONTAINER_MEMORY_LIMIT. But Id like to understand how this works from source to dest.

Example, if I set the request and memory limit to 2gb but the first sync is 10gb of rows, how will it be handled? First 2gb of rows goes to disk? And when airbyte goes to send this to dest, will it be batches of 2gb, or something like that? I really appreciate any link to docs, discussion or article that answers things like that.

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

Hi @Soufraz, this is a great question.

Firstly, it depends on what type of connector you’re using. If you’re using a source connector: sources read data in batches. It’s not possible to know what the size of these batches are before reading them. For destination connectors: destinations read records until they hit a batch size, which is currently set at 10k records. This can cause out of memory errors for tables with large row sizes, which perhaps you’ve experienced.

Admittedly, I don’t believe we have clarifying documentation relating to this but we welcome any contributions to our docs that can help the community. Let me know if I answered your question and apologies for the delay.