Consider to speed up the generating process

[Liam0205]

I agree and want to create new issue

• Yes, I was on Hexo Docs page, especially on Templates, Variables, Helpers and Troubleshooting.
• Yes, I was on NexT Documentation Site.
• And yes, I already searched for current issues and this is not help to me.

---

Expected behavior

When I was using old version of NexT (0.x), generating 250+ posts costs around 1.4 minutes. I consider this is the expected behavior of Hexo generating speed.

Actual behavior

Now, generating 280 posts cost more than 7 minutes, and one day it costs me 20 minutes, which is not considered to be tolerated.

Steps to reproduce the behavior

$ hexo clean && time hexo generate

• Link to demo site with this feature: N/A
• Link(s) to source code or any usefull link(s): N/A

What I've tried

Here are what I've tried:

• specify programming language for code blocks in all posts, based on this post and this post.
• enable NexT's cache, introduced in version 6.0.0, based on Hexo theme NexT generate too much slower than default theme (landscape) #539 (comment).

NexT Scheme:

• All schemes
• Muse
• Mist
• Pisces
• Gemini

Hexo's and NexT's version number, configuration of Hexo and NexT, and environment information could be found in #658 .

[Liam0205]

Test for cache-disabled. disable_cache.log

$ hexo clean && time hexo generate > disable_cache.log 2>&1
INFO  Deleted database.
INFO  Deleted public folder.

real    10m40.752s
user    0m0.030s
sys     0m0.291s

Test for cache-enabled. (didn't get the announced 3x speed-up.)
enable_cache.log

$ hexo clean && time hexo generate > enable_cache.log 2>&1
INFO  Deleted database.
INFO  Deleted public folder.

real    7m58.032s
user    0m0.031s
sys     0m0.306s

[jiangtj]

Same issue in all schemes.
See https://hexo.io/docs/templates.html#Optimization.
Fragment Caching may be a good way, but it takes a lot of work.

[Liam0205]

Same issue in all schemes.

Scheme or theme? Is this a NexT specific problem? --- based on #539 , it seems to be.

See https://hexo.io/docs/templates.html#Optimization.
Fragment Caching may be a good way, but it takes a lot of work.

Do your team has a plan for this?

[ivan-nginx]

@Liam0205 issue will be fixed soon. I've already turnkey solution, need just to debug it.

[Liam0205]

@ivan-nginx Glad to know!

If there is any progress of it, or if any test task needed, please let me know.

[jiangtj]

I think use partial helper instead of include swig tag may be improved to some extent.

partial read data from theme.views object.
https://github.com/hexojs/hexo/blob/a6dc0ea28dddad1b5f1bad7c6f86f1e0627b564a/lib/plugins/helper/partial.js#L12

include read from disk file.

https://github.com/node-swig/swig-templates/blob/6209307105f609a54bdbbee4ca0cc156991a521c/lib/tags/include.js#L39-L51

[jiangtj]

#969 I don't have any ideas now. . .

[stevenjoezhang]

So... how do
https://github.com/hexojs/hexo-generator-tag
and
https://github.com/hexojs/hexo-generator-category
deal with _draft 😥

#42 #87

GitHub

hexojs/hexo-generator-tag

Tag generator plugin for Hexo. Contribute to hexojs/hexo-generator-tag development by creating an account on GitHub.

GitHub

hexojs/hexo-generator-category

Category generator plugin for Hexo. Contribute to hexojs/hexo-generator-category development by creating an account on GitHub.

[jiangtj]

https://github.com/hexojs/hexo/blob/b6394c78751d2be81c3fd7c243fca37c552cd83a/lib/plugins/helper/tagcloud.js#L196

Same, filter. We only used it in one place....

GitHub

hexojs/hexo

A fast, simple & powerful blog framework, powered by Node.js. - hexojs/hexo

[jiangtj]

https://github.com/hexojs/hexo-theme-landscape/blob/7e0bd67ddf5d41d161437e2343da5d45c076a072/layout/layout.ejs#L11

Cache...

GitHub

hexojs/hexo-theme-landscape

A brand new default theme for Hexo. Contribute to hexojs/hexo-theme-landscape development by creating an account on GitHub.

[Liam0205]

After #971 being merged, the generating speed is much faster than before.

My great appreciation would be shown to @jiangtj and the team for the continuous efforts on this issue.