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.

Sign up for GitHub

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 faster-run.md #4677

Closed
wants to merge 1 commit into from
Closed

Update faster-run.md #4677

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions website/docs/docs/dbt-versions/release-notes/79-July-2023/faster-run.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,11 +23,11 @@ For all its strengths, Kubernetes has challenges, especially with pod management

Jobs scheduled at the top of the hour used to take over 106 seconds to prepare because of the volume of runs the scheduler has to process. Now, even with increased runs, we have reduced prep time to 27 secs (at a maximum) — a 75% speed improvement for runs at peak traffic times!

## Unlimited job concurrency for Enterprise accounts
## Unlimited job concurrency for Enterprise and Team accounts
Copy link
Contributor

Choose a reason for hiding this comment

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

same as below and also to avoid any broken links

Suggested change
## Unlimited job concurrency for Enterprise and Team accounts
## Unlimited job concurrency for Enterprise accounts


Our enhanced scheduler offers more durability and empowers users to run jobs effortlessly.

This means Enterprise, multi-tenant accounts can now enjoy the advantages of unlimited job concurrency. Previously limited to a fixed number of run slots, Enterprise accounts now have the freedom to operate without constraints. Single-tenant support will be coming soon. Team plan customers will continue to have only 2 run slots.
This means Enterprise and Teams (multi-tenant accounts) can now enjoy the advantages of unlimited job concurrency. Previously limited to a fixed number of run slots, Enterprise and Team accounts now have the freedom to operate without constraints. Single-tenant support will be coming soon.
Copy link
Contributor

@mirnawong1 mirnawong1 Dec 20, 2023 •
edited
Loading

Choose a reason for hiding this comment

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

will add an update to this as oppose to changing the entire content since release note are more of a 'point in time'

Suggested change
This means Enterprise and Teams (multi-tenant accounts) can now enjoy the advantages of unlimited job concurrency. Previously limited to a fixed number of run slots, Enterprise and Team accounts now have the freedom to operate without constraints. Single-tenant support will be coming soon.
This means Enterprise, multi-tenant accounts can now enjoy the advantages of unlimited job concurrency. Previously limited to a fixed number of run slots, Enterprise accounts now have the freedom to operate without constraints. Single-tenant support will be coming soon. Team plan customers will continue to have only 2 run slots.


Something to note, each running job occupies a run slot for its duration, and if all slots are occupied, jobs will queue accordingly.

Expand Down
Loading