Announce new default build spec#3098
Conversation
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip GraphQL API works alongside REST and WebSocket protocols |
Greptile SummaryThis PR announces the upgraded default build specification for Appwrite Cloud Sites and Functions — raising the default from 0.5 CPU / 512 MB to 2 CPU / 2 GB — through a new changelog entry and consistent updates across the compute billing, functions, and sites documentation pages.
Confidence Score: 4/5Safe to merge — all changes are documentation updates with no executable code, and the information is consistent across all four files. The spec table, info note, functions page, and sites page all agree on the new build default (2 CPU / 2 GB) and the removal of lower build tiers. The one gap is that the changelog doesn't mention the GB-hour rate impact on Free plan builds, which could surprise some users. src/routes/changelog/(entries)/2026-07-14.markdoc — consider adding a note about build GB-hour consumption for Free plan users. Important Files Changed
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
src/routes/changelog/(entries)/2026-07-14.markdoc:9
**Free plan GB-hour consumption not mentioned**
The changelog says the change "requires no configuration changes," which is accurate, but it omits the billing side-effect for Free plan users. Build GB-hours are calculated as memory (GB) × build duration. Moving from 512 MB (0.5 GB) to 2 GB quadruples the GB-hour rate during builds — even if builds finish faster, users whose builds are memory-bound rather than CPU-bound may not see proportional speed gains and could exhaust their 100 GB-hour Free plan budget faster than before. A brief note (e.g., "Free plan build GB-hour consumption may increase; faster builds typically offset this") would set correct expectations.
Reviews (1): Last reviewed commit: "Announce new default build spec" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
|
||
| We have upgraded the default build specification for Appwrite Sites and Functions on Cloud. Every deployment build now runs with **2 CPU cores and 2GB of memory**, replacing the previous 0.5 CPU and 512MB default. Lower build specifications have been removed. | ||
|
|
||
| The new default applies to all plans, including Free, and requires no configuration changes. Expect faster dependency installs, compilation, and bundling across your sites and functions. Runtime specifications are unaffected by this change. |
There was a problem hiding this comment.
The changelog says the change "requires no configuration changes," which is accurate, but it omits the billing side-effect for Free plan users. Build GB-hours are calculated as memory (GB) × build duration. Moving from 512 MB (0.5 GB) to 2 GB quadruples the GB-hour rate during builds — even if builds finish faster, users whose builds are memory-bound rather than CPU-bound may not see proportional speed gains and could exhaust their 100 GB-hour Free plan budget faster than before. A brief note (e.g., "Free plan build GB-hour consumption may increase; faster builds typically offset this") would set correct expectations.
Prompt To Fix With AI
This is a comment left during a code review.
Path: src/routes/changelog/(entries)/2026-07-14.markdoc
Line: 9
Comment:
**Free plan GB-hour consumption not mentioned**
The changelog says the change "requires no configuration changes," which is accurate, but it omits the billing side-effect for Free plan users. Build GB-hours are calculated as memory (GB) × build duration. Moving from 512 MB (0.5 GB) to 2 GB quadruples the GB-hour rate during builds — even if builds finish faster, users whose builds are memory-bound rather than CPU-bound may not see proportional speed gains and could exhaust their 100 GB-hour Free plan budget faster than before. A brief note (e.g., "Free plan build GB-hour consumption may increase; faster builds typically offset this") would set correct expectations.
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
1 participant
What does this PR do?
(Provide a description of what this PR does.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)