-
-
Notifications
You must be signed in to change notification settings - Fork 33.4k
src: add V8 Fast API for URL.revokeObjectURL
#58544
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
src: add V8 Fast API for URL.revokeObjectURL
#58544
Conversation
b6efadf
to
6c550e4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should stop implementing C++ APIs twice. I don't mean to ban usage of V8 Fast API, but there should be only one implementation, that is called from both regular and fast API callbacks.
There have already been regressions because of multiple implementations that were not kept in sync.
7c628fb
to
659e3c0
Compare
co-authored-by: Nicholas Paun <npaun@cloudflare.com>
659e3c0
to
77fd7b8
Compare
silence cpp lint error
add RevokeObjectURLImpl to share logic
Thanks so very much for the comment @targos 🙏 I totally agree with the suggestion 🙂 , does this look good? 🙂 🙏 e947f44 |
fix cpp formatting
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #58544 +/- ##
==========================================
+ Coverage 90.21% 90.24% +0.02%
==========================================
Files 635 635
Lines 187580 187603 +23
Branches 36853 36857 +4
==========================================
+ Hits 169231 169300 +69
+ Misses 11108 11057 -51
- Partials 7241 7246 +5
🚀 New features to boost your workflow:
|
skip test on no crypto
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I read the benchmark results correct it is a five percent regression?
This would align with other benchmarks with a couple of the "fast" API changes. They often turn out to be slower than before.
I am just requesting changes to verify that. If it's not an issue, please feel free to dismiss my request.
Could you add your benchmark to the code to run it on our machines?
darn it, you're totally right, sorry I was so fixated on the number that I missed which was the faster one.... I was sure to have seen at some point my implementation be faster than node... but I might be misremembering it 😖 Thanks so much for catching it @BridgeAR!!! 🫶 and so sorry for my mistake! 😓 I've re-run the hyperfine command multiple times and on my machine yeah I am consistently getting this sort of result 😓 At this point I am completely fine closing this PR, and open a new PR to either remove this todo comment: Line 453 in 0e157b6
or convert it to a comment explaining the the fast API doesn't help here how does that sound @BridgeAR? @anonrig? (or maybe my implementation is flawed?) |
Benchmarking results:

(not a huge perf improvement 😓)
PS: I've done this alongside @npaun, thanks a lot Nicholas for working this out with me and your C++ tips/guidance 🫶