-
Notifications
You must be signed in to change notification settings - Fork 50
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
Improving rendering performance #92
Comments
Based on some experimentation not running the body of every article through the markdown parser seems to make a significant difference in the performance.
Without parsing the markdown content
Also, an added benefit of not parsing the markdown content is that once the rhai shortcodes #91 gets merged, the performance of pages that don't use shortcodes will not incur a performance penalty due to other pages utilizing shortcodes. |
While working on #91, I noticed that the content body of every
.md
file is parsed on every request. This induces a potential performance hit. I feel like this could be an area for performance optimization of the rendering process as I think it is unnecessary to parse the markdown content of files other than the one that is requested. The required details for the post can be obtained from the header.I realize that this would disrupt the way in which the posts in a blog would be listed where the content appears below the title but I feel like it is a problem that can be solved by using the description in the
head
. One compromise would be to only parse the markdown if thehead.description
is empty.Any thoughts?
The text was updated successfully, but these errors were encountered: