Skip to content
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

Update job-scheduler.md #3737

Closed
wants to merge 3 commits into from
Closed

Update job-scheduler.md #3737

wants to merge 3 commits into from

Conversation

schottj
Copy link
Contributor

@schottj schottj commented Jul 13, 2023

run slots update

@schottj schottj requested a review from a team as a code owner July 13, 2023 21:16
@netlify
Copy link

netlify bot commented Jul 13, 2023

Deploy Preview for docs-getdbt-com ready!

Name Link
🔨 Latest commit dc13ed5
🔍 Latest deploy log https://app.netlify.com/sites/docs-getdbt-com/deploys/64b53f82939eaa0008182bb0
😎 Deploy Preview https://deploy-preview-3737--docs-getdbt-com.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@github-actions github-actions bot added content Improvements or additions to content size: x-small This change will take under 3 hours to fix. labels Jul 13, 2023
@@ -31,7 +31,7 @@ Familiarize yourself with these useful terms to help you understand how the job
| Over-scheduled job | A situation when a cron-scheduled job's run duration becomes longer than the frequency of the job’s schedule, resulting in a job queue that will grow faster than the scheduler can process the job’s runs. |
| Prep time | The time dbt Cloud takes to create a short-lived environment to execute the job commands in the user's cloud data platform. Prep time varies most significantly at the top of the hour when the dbt Cloud Scheduler experiences a lot of run traffic. |
| Run | A single, unique execution of a dbt job. |
| Run slot | Run slots control the number of jobs that can run concurrently. Each account has a fixed number of run slots, depending on the plan tier, that are shared across projects in the account. Each running job occupies a run slot for the duration of the run, so purchasing more run slots enables more jobs to execute in parallel. |
| Run slot | Run slots control the number of jobs that can run concurrently. Each account has a fixed number of run slots, depending on the plan tier, that are shared across projects in the account. Each running job occupies a run slot for the duration of the run, so if you need more jobs to execute in parallel consider the enterprise tier. |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@schottj should we link to the pricing page?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @schottj , i think you opened a separate pr addressing the run slots. could we combine your changes here onto the other pr: #3712?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here are the changes for pr 3712:

| Run slot | Run slots control the number of jobs that can run concurrently. Developer and Team plan accounts have a fixed number of run slots, and Enterprise users have unlimited run slots. Each running job occupies a run slot for the duration of the run. If you need more jobs to execute in parallel, consider the Enterprise plan |

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mirna, you can change the base branch to PR #3712 or make this PR the base branch and merge them together (this might be what you were suggesting too.)

@mirnawong1
Copy link
Contributor

closing as it's the same as pr #3712 (review)

@mirnawong1 mirnawong1 closed this Jul 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content size: x-small This change will take under 3 hours to fix.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants