Skip to content

Commit

Permalink
Fix intervals
Browse files Browse the repository at this point in the history
  • Loading branch information
@igorlukanin
igorlukanin committed Feb 5, 2024
1 parent c5989da commit 25ffb13
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/pages/product/deployment/cloud/auto-suspension.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ deployment when API requests start coming in again:
/>

[Development instances][ref-deployment-dev-instance] are auto-suspended
automatically when not in use for 1 hour, whereas [production
automatically when not in use for 30 minutes, whereas [production
clusters][ref-deployment-prod-cluster] can auto-suspend after no API
requests were received within a configurable time period.

Expand Down
2 changes: 1 addition & 1 deletion docs/pages/product/deployment/cloud/deployment-types.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ query pre-aggregations on-demand.

Development instances do not provide high-availability nor do they guarantee
fast response times. Development instances also [auto-suspend][ref-auto-sus]
after 1 hour of inactivity, which can cause the first request after the instance
after 30 minutes of inactivity, which can cause the first request after the instance
wakes up to take additional time to process. They also have [limits][ref-limits]
on the maximum number of queries per day and the maximum number of Cube Store
Workers. We **strongly** advise not using a development instance in a production
Expand Down

0 comments on commit 25ffb13

Please sign in to comment.