Review Neko to increase performance and reduce memory usage
This is just a bookmark for my ongoing task of tuning without larger rewrites. So far, we got to this:
Wikipedia DE Homepage, DOM Parser, JDK 17, JDK 8 target
Old, v3.8.0
Benchmark Mode Cnt Score Error Units
HtmlParser_v380_Benchmark.domParser avgt 3 1,596,511 ± 136,413 ns/op
HtmlParser_v380_Benchmark.domParser:gc.alloc.rate.norm avgt 3 1,091,867 ± 1,868 B/op
New, JDK 8 target
Benchmark Mode Cnt Score Error Units
HtmlParser_v380_Benchmark.domParser avgt 3 1,178,706 ± 130,720 ns/op
HtmlParser_v380_Benchmark.domParser:gc.alloc.rate.norm avgt 3 870,992 ± 0 B/op
New, JDK 11 target
Benchmark Mode Cnt Score Error Units
HtmlParser_v380_Benchmark.domParser avgt 3 1,165,087 ± 112,361 ns/op
HtmlParser_v380_Benchmark.domParser:gc.alloc.rate.norm avgt 3 870,656 ± 0 B/op
Summary: 25% faster and 20% less memory is needed. There are 1-2% more performance in a JDK 11 compile than a JDK 8 one due to improvements of the JDK 11 code generation (no accessor methods for inner classes anymore).
HtmlUnit / htmlunit-neko
HtmlUnit adaptation of NekoHtml
17
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too