[codex] add object storage provider benchmark post#7985
Draft
sorenbs wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The draft evaluates Cloudflare R2 and Tigris for Prisma Compute using the
accelerated-fsworkload. The post makes the benchmark results easier to read with inline charts and keeps the claims scoped to the measured latency-sensitive filesystem workload.Validation
pnpm --filter blog types:checkhttp://localhost:3002/blog/evaluating-object-storage-providers-for-prisma-computefor title, author, series marker, generated hero image, Mermaid diagram, and both SVG charts.Notes
The local dev page shows unrelated analytics/cookie-script errors in browser logs on localhost, but the post content and assets render correctly.