-
Notifications
You must be signed in to change notification settings - Fork 368
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
c6e331f
commit d3ac6e4
Showing
2 changed files
with
29 additions
and
1 deletion.
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
--- | ||
title: Resource Limits | ||
--- | ||
|
||
Resource limits are a way to limit the maximum amount of resources available to a service. | ||
|
||
## Configure Resource Limits | ||
|
||
You can update resource limits from the service settings page under the "Deploy" section. | ||
|
||
<Image | ||
src="https://res.cloudinary.com/railway/image/upload/v1721917970/resource-limits.png" | ||
alt="Resource Limits setting" | ||
layout="intrinsic" | ||
width={1298} | ||
height={658} | ||
quality={80} | ||
/> | ||
|
||
### Use Resource Limits | ||
|
||
Using resource limits makes sense in scenarios where: | ||
|
||
1. You don't want to risk a high bill due to unexpected spikes in usage. | ||
2. You are okay with the service possibly crashing if it exceeds the limit, possibly in non-production environments. | ||
|
||
**Note**: We do not recommend using resource limits in production environments as setting your limits too low can cause your service to crash. |