Posthog- Sync Speed can't catch up with source emition speed

Connector Questions & Issues
,
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Digital Ocean 16 GB Memory / 320 GB Disk / LON1 - Ubuntu 20.04 (LTS) x64
  • Memory / Disk: 16 GB Memory / 320 GB Disk
  • Deployment: Docker
  • Airbyte Version: 0.46.26
  • Source name/version: Posthog 0.1.8
  • Destination name/version: Snowflake
  • Step: Sync
  • Description: I’ve tested different ways to scale up my instance like changing instance type, increasing number of workers etc but nothing seems to affect the speed at which records are fetched from the source . At current speed around 120 records per second, we cannot reasonibly keep up with how much records are created. Is there something we could change in the connector set up to increase pagination or batch size ? It currently fetches around 1k records every 10 sec or 200KB/s. Which seems very low to me.

Here is below the sum up of my attempts :


"totalStats" : {
  "recordsEmitted" : 10423,
  "bytesEmitted" : 20604648,
  "sourceStateMessagesEmitted" : 6,
  "destinationStateMessagesEmitted" : 1,
  "recordsCommitted" : 10423,
  "meanSecondsBeforeSourceStateMessageEmitted" : 50,
  "maxSecondsBeforeSourceStateMessageEmitted" : 101,
  "maxSecondsBetweenStateMessageEmittedandCommitted" : 112,
  "meanSecondsBetweenStateMessageEmittedandCommitted" : 112,
  "replicationStartTime" : 1671557994215,
  "replicationEndTime" : 1671558111458,
  "sourceReadStartTime" : 1671557994280,
  "sourceReadEndTime" : 1671558103216,
  "destinationWriteStartTime" : 1671557994336,
  "destinationWriteEndTime" : 1671558111457
  total  = 108936 source read duration in ms
  Speed = 0.0956 rec/ms -> 95rec/sec
  Size Speed = 0.000237MB/ms -> 0.23 Mo/s
}


10 Workers -  16 GB Memory / 320 GB Disk / LON1 - Ubuntu 20.04 (LTS) x64

"totalStats" : {
  "recordsEmitted" : 27876,
  "bytesEmitted" : 50633892,
  "sourceStateMessagesEmitted" : 6,
  "destinationStateMessagesEmitted" : 1,
  "recordsCommitted" : 27876,
  "meanSecondsBeforeSourceStateMessageEmitted" : 125,
  "maxSecondsBeforeSourceStateMessageEmitted" : 250,
  "maxSecondsBetweenStateMessageEmittedandCommitted" : 265,
  "meanSecondsBetweenStateMessageEmittedandCommitted" : 265,
  "replicationStartTime" : 1671558522403,
  "replicationEndTime" : 1671558794175,
  "sourceReadStartTime" : 1671558522450,
  "sourceReadEndTime" : 1671558783591,
  "destinationWriteStartTime" : 1671558522507,
  "destinationWriteEndTime" : 1671558794175
  total = 261141 source read duration in ms
  Speed = 0.106 rec/ms -> 106 rec/sec
  Size Speed = 0.000237MB/ms -> 0.23 Mo/s
}

10 Workers - 64 GB Memory / 320 GB Disk / LON1 - Ubuntu 20.04 (LTS) x64

"totalStats" : {
  "recordsEmitted" : 54378,
  "bytesEmitted" : 102999115,
  "sourceStateMessagesEmitted" : 6,
  "destinationStateMessagesEmitted" : 1,
  "recordsCommitted" : 54378,
  "meanSecondsBeforeSourceStateMessageEmitted" : 70,
  "maxSecondsBeforeSourceStateMessageEmitted" : 419,
  "maxSecondsBetweenStateMessageEmittedandCommitted" : 441,
  "meanSecondsBetweenStateMessageEmittedandCommitted" : 441,
  "replicationStartTime" : 1671560005379,
  "replicationEndTime" : 1671560454173,
  "sourceReadStartTime" : 1671560005412,
  "sourceReadEndTime" : 1671560440014,
  "destinationWriteStartTime" : 1671560005454,
  "destinationWriteEndTime" : 1671560454171

  total =  434602 source read duration in ms
  Rec Speed = 0.125 rec/ms -> 125 rec/sec
  Size Speed = 0.000237MB/ms -> 0.23 Mo/s```
2

I’ve looked deeper in the API specs and it looks like the limit parameter can be used to define batch size . Currently it is set in the code to 100, which is quite inefficient as it means hitting the API with loads of request. It is said in the code that the parameter is ignored which is partly wrong if the limit parameter is specified then then paginator will include it in the next request URL effectively modulating the batch size.

Opening a pull request to either increase the batch size to 10k or be able to set it up at source specification level.

3

Issue : [Source Connector] - Posthog - API batch size increase to improve Sync Speed · Issue #20751 · airbytehq/airbyte · GitHub

4

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.
Best,
The Community Assistance Team

5

Hello Guillaume Chevalier, it’s been a while without an update from us. Are you still having problems or did you find a solution?

6

Hey Sajarin the problem still occures, in the meantime i switched to another ingestion provider