-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Facebook Marketing performance improvement #8385
Conversation
/test connector=connectors/source-facebook-marketing
|
7ba1169
to
17147fe
Compare
/test connector=connectors/source-facebook-marketing
|
/publish connector=connectors/source-facebook-marketing run-test=false
|
/publish connector=connectors/source-facebook-marketing run-tests=false
|
5500f20
to
69b2958
Compare
/test connector=connectors/source-facebook-marketing
|
@@ -13,21 +13,10 @@ tests: | |||
- config_path: "secrets/config.json" | |||
basic_read: | |||
- config_path: "secrets/config.json" | |||
configured_catalog_path: "integration_tests/configured_catalog.json" | |||
timeout_seconds: 600 | |||
empty_streams: ["videos"] | |||
incremental: | |||
- config_path: "secrets/config.json" | |||
configured_catalog_path: "integration_tests/configured_catalog_without_insights.json" | |||
future_state_path: "integration_tests/future_state.json" | |||
full_refresh: | |||
- config_path: "secrets/config.json" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
means we test all streams from the catalog, and because we using new PK-based comparison we don't need to ignore some fields
Co-authored-by: Eugene Kulak <[email protected]>
Resolves #8282
Improve performance for getting Ads Insights metrics over async jobs.
In previous version we had constant number (10) of simultaneously running async jobs for ads insights.
Since there is no limit on concurrent async jobs number from facebook side ( there is only ads insights throttle parameter that displays how much facebook throttling our jobs execution) so in this PR algorithm is following:
Notes:
Here is simple performance test Ive done trying to run it with different "days per job" parameter, time range was 2019-05-23 - 2021-11-02. All test were run on test account with very few data and single run so it just rough estimate on how much time it takes to run:
Also I tried to run it on maximum allowed range of 37 monthes with 1 day per job. It spawned maximum of 1109 concurrent jobs and took 16:15 to complete. There were no fails were detected for all test runs.
This change is![Reviewable](https://camo.githubusercontent.com/1541c4039185914e83657d3683ec25920c672c6c5c7ab4240ee7bff601adec0b/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)