Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
tpl: Add findRE template func #2048
The setup: I copied the content of a file from the docs in the default archetype. Next, I wrote a small bash script that generates 400 new content files (is this medium sized?). Finally, I build the site. The benchmark of course does only include the build time of the website not the generation of the content files.
This are the results without regexp:
and with the complete scrollspy regexp:
As you can see the difference if marginal with such a simple regexp.
Thanks for pointing me to the reCache. I tested it a couple of times and got on average the following result:
Under the line a good improvement of 40ms .
People that are using regexp should know what they're getting into. Let's wait and see how it unfolds. If we start getting a bunch of people confused about why their builds are slow, we can consider updating the docs.
Although, I don't think it will be that much of a slowdown, anyway. The Go RE engine won't blow up in your face like all the other back-referencing engines can.