| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
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.
Sorry, something went wrong.
co-authored-by: Nicholas Paun <npaun@cloudflare.com>
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 |
Sorry, something went wrong.
fix cpp formatting
Sorry, something went wrong.
Codecov ReportAttention: Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
@@ 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
... and 32 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
skip test on no crypto
Sorry, something went wrong.
There was a problem hiding this comment.
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?
Sorry, something went wrong.
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?) |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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 🫶