Update faster-run.md #4677
Closed
Update faster-run.md #4677
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
mirnawong1
reviewed
Dec 20, 2023
|
|
||
| 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. |
There was a problem hiding this comment.
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. |
mirnawong1
reviewed
Dec 20, 2023
| @@ -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 | |||
There was a problem hiding this comment.
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 |
|
hey @wusanny thanks so much for this brilliant contribution! I've made some changes in your first PR https://github.com/dbt-labs/docs.getdbt.com/pull/4676/files and added an 'update' section to the release note. i hope you don't mind and i'll close this PR to keep the convo in the other one. thank you again! |
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.
What are you changing in this pull request and why?
Team plans was updated a while back, this is to update the information on docs
Checklist
Adding new pages (delete if not applicable):
website/sidebars.jsRemoving or renaming existing pages (delete if not applicable):
website/sidebars.jswebsite/static/_redirectsnpm run buildto update the links that point to the deleted page