-
Notifications
You must be signed in to change notification settings - Fork 247
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
feat(query-engine-wasm): exclude native-drivers only errors from wasm32
target
#4616
Conversation
…rom wasm32 target
WASM Size
|
CodSpeed Performance ReportMerging #4616 will not alter performanceComparing Summary
|
✅ WASM query-engine: no benchmarks have regressedFull benchmark report
After changes in 5ad7d0b |
There are a bunch of clippy issues, such as:
|
Background info: if we introduced a Having a large |
This comment was marked as resolved.
This comment was marked as resolved.
Thank you for your reply.
No, I’m saying it would impact memory allocation in query-engine-node-api and the binary query-engine . It would have 0 effects on Wasm, as when targeting wasm32 we’d have an enum with a single variant |
…o" on Wasm, to shove off a few bytes
Then I think it will be negligible, given it happens once per query. Go ahead and check benchmarks, if there's no regression, then we will know we are good. |
wasm32
targetwasm32
target
Vitess 8 is failing, I'll look into it but it doesn't seem related to this PR: https://github.com/prisma/prisma-engines/actions/runs/7339908596/job/19985031968?pr=4616#step:12:2364 |
…risma/prisma-engines into feat/exclude-native-errors-from-wasm32
(There are a couple of hiccups to fix, as per CI. I'm on it) |
Update: found the problem and solved it. |
This PR is a follow-up of #4615.
This PR closes https://github.com/prisma/team-orm/issues/763.
This PR contributes to https://github.com/prisma/team-orm/issues/584.
The current reduction of the gzip'd bundle size is around ~9 KB.