benchmark with markdown-it

[Mister-Hope]

Summary

Adding a benchmark comparison with markdown-it

Motivation

This feature allows people to compare the performance of the current new library.

Though docs mentions a (~30% reduction), but I don't think this is worth considering in most cases. Performance should take the first place :)

For me, I would doubt the performance with the introduction with async renderers with contents just rendered by sync rules (e.g.: markdown that supposed to render under GFM)。

BTW, memory usage should be another important data that should contain in benchmark besides time.

Proposed Solution

I see a bench folder in packages, but it does not have any description.

Anyway, if you want more people to switch to your lib, you'd better include it in your docs.

We currently consider it for VuePress v2 and the integration for mdit-plugins

Would you like to work on this new feature?

• I'm interested in working on this new feature

  Sorry no, I can surely add a simple one, but I am not the one who writes the code. I think it's better for the author to add some worth comparing cases in benchmark.

[Mister-Hope]

Interesting to find this post from your blog:

Competing with Existing Open-Source Projects

If your open-source project competes with similar products on the market, you need to ensure the project's quality is "super good". You must give users a reason to choose your project; otherwise, they may not be willing to learn a product similar to existing solutions when it is first launched, due to insufficient community support, usage discussions, and third-party libraries.

[serkodev]

Thanks for the suggestion. This project still in beta stage, there are still some refactoring tasks on the to-do list, and once the architecture is updated and the performance is optimized, I'll add the benchmark results to the documentation.