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 new blog post and changelog entry announcing parallel chunk uploads in Appwrite SDKs, alongside supporting documentation updates across the REST API reference, storage service description, and CLI buckets page.
Confidence Score: 5/5Safe to merge — this is a content-only PR (blog post, changelog, and doc updates) with no executable code changes. All changes are Markdoc/Markdown content. There are no runtime logic changes, migrations, or API surface changes. The two flagged items are copy quality issues in the blog post that do not affect the site's functionality. The blog post (+page.markdoc) has a React Native snippet with undefined variables and an ambiguous upgrade path for self-hosted users — worth a quick author pass before the post goes live. Important Files Changed
Reviews (6): Last reviewed commit: "mention Console also benefits from paral..." | Re-trigger Greptile |
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.
The cache entry records
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", |


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.)