Performance page update with parallelism pitfalls section #2240
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for dlt-hub-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| @@ -6,7 +6,13 @@ keywords: [scaling, parallelism, finetuning] | |||
|
|
|||
| # Optimizing dlt | |||
|
|
|||
| ## Yield pages instead of rows | |||
| This page contains a collection of tips and tricks to optimize dlt pipelines for speed, scalability and memory footprint. | |||
|
|
|||
There was a problem hiding this comment.
I would add here a small reminder that dlt works in three steps and link this page https://dlthub.com/docs/reference/explainers/how-dlt-works
|
|
||
| Instead of using Python Requests directly, you can use the built-in [requests wrapper](../general-usage/http/requests) or [`RESTClient`](../general-usage/http/rest-client) for API calls. This will make your pipeline more resilient to intermittent network errors and other random glitches. | ||
| 2. If you are running pipelines in parallel against the same destination dataset and are using a staging destination, you should change the staging destination bucket subfolder to be unique for each pipeline or alternatively disable cleaning up the staging destination after each load for all pipelines: [how to prevent staging files truncation](../dlt-ecosystem/staging#how-to-prevent-staging-files-truncation) If you do not, files might be deleted by one pipeline that are still required to be loaded by another pipeline running in parallel. |
There was a problem hiding this comment.
can you rephrase it in a clearer way? something like:
2. If you're running multiple pipelines in parallel that write to the same destination dataset and use a staging area, make sure to do one of the following:
a. Assign a unique subfolder in the staging destination bucket for each pipeline, or
b. [Disable automatic cleanup of the staging area](../dlt-ecosystem/staging#how-to-prevent-staging-files-truncation) after each load for all pipelines.
If you don’t do this, one pipeline might delete staging files that are still needed by another pipeline running at the same time.
Co-authored-by: Alena Astrakhantseva <[email protected]>
Co-authored-by: Alena Astrakhantseva <[email protected]>
…to docs/update-performance-page
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR does the following: