Skip to main content

Community

Connector Improvement: Improve Performance of PostHog Connector

Answered

Please sign in to leave a comment.

Comments

2 comments

  • Official comment

    Hi Michael,

    This is a valuable request. We've added your feedback on PostHog connector performance to our feature improvements backlog. To help us prioritize enhancements, could you share more about your primary use case? Specifically, are there certain analytics or reporting objectives being hindered by the current sync frequency? Additionally, any details on data volume or typical sync windows that would meet your needs would be useful.

    We'll keep this thread updated as we make progress on improvements.

     

    Thanks,
    Syead

    We have a handful of use cases, like operational analytics for downstream integrations, that require fresher data, but all insights are currently at least a full day behind and will only get worse as we scale.

    Even setting use cases aside, this Lite connector just isn’t very good. The main reason we’re using it instead of syncing directly from PostHog to Fivetran is the number of projects we have; managing individual syncs would be a cumbersome endeavor.

    For context, we’re processing ~40M events per day. Current sync times range from 21–27 hours, and syncs frequently fail with the error: “Infrastructure rescheduled sync for appropriate resource provisioning