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
Move more parsing in stage2 #74
Conversation
Codecov Report
@@ Coverage Diff @@
## 0.2 #74 +/- ##
==========================================
- Coverage 84.67% 84.08% -0.59%
==========================================
Files 34 35 +1
Lines 4410 4462 +52
==========================================
+ Hits 3734 3752 +18
- Misses 676 710 +34
Continue to review full report at Codecov.
|
@sunnygleason I think this part of 0.2 is ready to take a peek :) |
This reverts commit 2456be7. Negative perf impact
The latest change isn't a clear win or loss but it moves the results a little:
Canada improves (which was our slowest case) but citm and twitter degrade slightly for parsing the Dom. On structs it is a win throughout the bench. I think even so two of the benchmarks degrade a bit, it's still a win at the end. |
Seems we're getting some memory corruption with this - any help with bug hunting welcome I've so far come up blank :/ |
Found the error it was a simple |
merging into 0.2 branch - we can review there. |
We can move some of the parsing logic into stage 2 instead of checking them after that. This simplifies the code for parse() .
Performance wise it looks like a small improvement too.
0.2
this