new blog for parallel chunk uploads#2966
Conversation
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Appwrite has crossed the 50K GitHub stars milestone with hundreds of active contributors |
Greptile SummaryThis PR adds a blog post and changelog entry announcing parallel chunk uploads in Appwrite SDKs, and updates the REST API, storage reference, and CLI documentation to reflect the new behavior.
Confidence Score: 5/5This PR is safe to merge — it is purely additive content and documentation with no logic changes. All changes are blog post content, changelog copy, and documentation prose updates. There are no code logic changes, schema changes, or API contract modifications. Previously flagged issues in the review thread have been noted or addressed. No files require special attention. Important Files Changed
Reviews (8): Last reviewed commit: "Rename changelog file to match date" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Replace projected speedups with Node SDK benchmark table (1.07x at 10 MB up to 7.10x at 1.28 GB). Drop the runtime hedge paragraph since PR #1498 ships parallel uploads in every SDK. Expand multicode block from 4 to 15 samples covering all client and server SDKs.
# Conflicts: # .optimize-cache.json
| "static/images/blog/everything-new-with-appwrite-1.5/1.5-recap.png": "1d3c646f6902757152d98861630c1952631a54f222af7f8476f53f4d0d3c59f2", | ||
| "static/images/blog/everything-new-with-appwrite-1.5/messaging-console.png": "769b7df74c9107a5ccacfe87722293adbfbd91ab702c79b03838c2368e9971ac", | ||
| "static/images/blog/examples-of-vibe-coding/cover.png": "745d0e65c7981fe852b2e1797c3163cd4e4c147227b906cf305019137cb4624f", | ||
| "static/images/blog/faster-storage-uploads-parallel-chunks/cover.png": "4565a9b19b4cafad3ed9ca3f2d4c6e4437379c5d10de6bad64dc1fb85590e49b", |
There was a problem hiding this comment.
cover.png, but the actual image added in this PR is cover.avif. This means the optimize-cache will never match the real file on disk, so the image either goes un-optimized or causes a spurious cache miss on every build.
| "static/images/blog/faster-storage-uploads-parallel-chunks/cover.png": "4565a9b19b4cafad3ed9ca3f2d4c6e4437379c5d10de6bad64dc1fb85590e49b", | |
| "static/images/blog/faster-storage-uploads-parallel-chunks/cover.avif": "4565a9b19b4cafad3ed9ca3f2d4c6e4437379c5d10de6bad64dc1fb85590e49b", |
|
@copilot change the announcement blog date in this PR to 18th May 2026, and same for changelog. DO NOT make any other changes. |
Agent-Logs-Url: https://github.com/appwrite/website/sessions/bdb7e5d0-3594-4101-906e-6497dc7c73b5 Co-authored-by: atharvadeosthale <11805367+atharvadeosthale@users.noreply.github.com>
| --- | ||
| layout: changelog | ||
| title: "Up to 7x faster Appwrite Storage uploads with parallel chunks" | ||
| description: Appwrite SDKs now upload Storage chunks in parallel on runtimes with native concurrency. Our Node SDK benchmarks show up to 7.10x faster uploads on large files, with no API changes for developers. | ||
| date: 2026-05-18 | ||
| cover: /images/blog/faster-storage-uploads-parallel-chunks/cover.avif |
There was a problem hiding this comment.
The file is named 2026-05-15-1.markdoc but its frontmatter declares date: 2026-05-18. Looking at the existing entry pattern (e.g. 2026-05-15.markdoc has date: 2026-05-15), the filename is used as the sort key for rendering the changelog. This entry will be sorted and displayed as May 15, three days before its stated publication date, causing it to appear out of order relative to other May 18 content.
There was a problem hiding this comment.
@copilot address this, change the file name to the date in frontmatter
Agent-Logs-Url: https://github.com/appwrite/website/sessions/d13793c4-edbc-4544-8068-53d3d8808d0e Co-authored-by: atharvadeosthale <11805367+atharvadeosthale@users.noreply.github.com>
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.)