-
Notifications
You must be signed in to change notification settings - Fork 131
chore: update examples #2461
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
chore: update examples #2461
Conversation
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Deploying rivet with
|
| Latest commit: |
0ae3f40
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://23ad5076.rivet.pages.dev |
| Branch Preview URL: | https://05-20-chore-update-examples.rivet.pages.dev |
0ae3f40 to
7e8648f
Compare
7e8648f to
ea6a78e
Compare
Merge activity
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
Updated pricing documentation with more granular core allocations and revised cost calculations for different deployment scenarios.
- Modified core allocations in
/site/src/content/docs/pricing.mdxfrom 1/8th to 1/64th for functions and 1/32nd for actors - Updated sample scenarios with more accurate cost calculations (e.g., 1M function calls @ 50ms now costs $0.009)
- Added clarification that 1/8th core minimum applies specifically to Containers
- Improved readability of storage pricing examples with clearer formatting
1 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile
| | 1M function calls @ 50ms | Stateless function | 1/64 core | 1M × 50ms = 50M → ÷64 = 0.78125M | $0.009 | | ||
| | Agents (Actors) | 500 actors × 30min/day | 1/32 core | 500 × 1800s × 30 = 27B → ÷32 = 843.75M | $9.44 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logic: Core-ms calculation for agents appears incorrect. 500 × 1800s × 30 = 27M (not 27B), which affects the final cost calculation.
| | 1M function calls @ 50ms | Stateless function | 1/64 core | 1M × 50ms = 50M → ÷64 = 0.78125M | $0.009 | | |
| | Agents (Actors) | 500 actors × 30min/day | 1/32 core | 500 × 1800s × 30 = 27B → ÷32 = 843.75M | $9.44 | | |
| | 1M function calls @ 50ms | Stateless function | 1/64 core | 1M × 50ms = 50M → ÷64 = 0.78125M | $0.009 | | |
| | Agents (Actors) | 500 actors × 30min/day | 1/32 core | 500 × 1800s × 30 = 27M → ÷32 = 0.84375M | $0.009 | |
| | 1M function calls @ 50ms | Stateless function | 1/64 core | 1M × 50ms = 50M → ÷64 = 0.78125M | $0.009 | | ||
| | Agents (Actors) | 500 actors × 30min/day | 1/32 core | 500 × 1800s × 30 = 27B → ÷32 = 843.75M | $9.44 | | ||
| | Compute-heavy container (10h) | Full CPU usage | 1 core | 10h = 36,000,000 | $0.40 | | ||
| | Storage-heavy app | 10GB storage, 5M reads, 1M writes | - | 10GB × $0.20 = $2.00(5M–1M) reads = $0.80(1M–1M) writes = $0.00 | $2.80 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
style: Storage cost calculation formatting needs spaces between components: '$2.00 + (5M–1M) reads = $0.80 + (1M–1M) writes = $0.00'
<!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->

Changes