-
Notifications
You must be signed in to change notification settings - Fork 248
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
Revert "qe: add json serialization span in binary engine" #4824
Merged
jkomyno
merged 1 commit into
main
from
revert-4339-qe-add-json-seriaization-span-in-binary-engine
Apr 11, 2024
Merged
Revert "qe: add json serialization span in binary engine" #4824
jkomyno
merged 1 commit into
main
from
revert-4339-qe-add-json-seriaization-span-in-binary-engine
Apr 11, 2024
Conversation
This file contains 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
This reverts commit fce8aba.
WASM Query Engine file Size
|
CodSpeed Performance ReportMerging #4824 will degrade performances by 5.45%Comparing Summary
Benchmarks breakdown
|
✅ WASM query-engine performance won't change substantially (0.989x)Full benchmark report
After changes in 2f7b510 |
Merging this in agreement with @aqrln. |
jkomyno
deleted the
revert-4339-qe-add-json-seriaization-span-in-binary-engine
branch
April 11, 2024 08:41
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.
Reverts #4339
This works with normal binary engine but breaks tracing with data proxy (i.e.
mini-proxy
and Accelerate) because these changes are not compatible withTracingConfig::Captured
and sending traces as part of the response.With the widened scope of the
prisma:engine
span, it is not closed by the time the traces are captured to be added to the response. In addition, it is fundamentally impossible to send the addedprisma:engine:response_json_serialization
with captured traces as it will pose a chicken and egg problem: the information about the time it took to prepare the JSON response would need to be a part of the same response.While it is possible to add some conditional logic to keep the new (consistent with the Node-API) behaviour for the normal binary engine (without data proxy / accelerate) with traces in stdout but revert to the old behaviour when captured traces in HTTP response are enabled, for now it is easier to just revert the commit. We don't use binary engine except to power Accelerate nowadays much anyway.