Use meeseeks_html5ever instead of html5ever_elixir #2
Because html5ever_elixir was designed with Floki's use in mind it parses strings of HTML into the tuple-tree format that
meeseeks_html5ever is designed for Meeseeks, and it parses strings of HTML directly into the
Floki parses html into tuple-trees, uses those tuple-trees to create a flat-map structure like
Meeseeks takes a different approach.
I chose this approach because it doesn't delay the building of the
There is a significant performance cost in converting a tuple-tree into a
I created a custom html5ever NIF, meeseeks_html5ever, that parses HTML directly into a
Performance is always a bit tricky to judge, but I've seen around a 30% increase in parse speed for large documents when using meeseeks_html5ever instead of html5ever_elixir.