-
Notifications
You must be signed in to change notification settings - Fork 185
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
Site build is slooow #81
Comments
What's your result with default theme? |
A bit shocking actually:
Elegant gives:
|
My test before any changes time pelican --settings settings.py
Done: Processed 280 articles and 1 pages in 40.54 seconds.
real 0m40.985s
user 0m40.571s
sys 0m0.377s |
After the fix time pelican --settings settings.py
Done: Processed 280 articles and 1 pages in 9.82 seconds.
real 0m10.239s
user 0m9.579s
sys 0m0.358s |
@tshepang thanks a lot for reporting this issue. It didn't come across my mind to compare Elegant's performance against other themes. I do not have a large blog yet that is why I didn't face these issues. I ran tests several times and it seems it takes on 9.18 seconds on average to process 280 articles and 1 pages. It is almost same as default theme. I deduce we have removed the major bottleneck in the performance. Unfortunately, it means for the users to use Kindly run profiler again and let me know if you find any other bottleneck or performance issue. |
\0/ \0/ \0/ |
Using the plugin gives about the same, fast performance. How come? I expected it to be super-slow. |
Plugin calculates the next and previous article during generation phase. Elegant used to iterated through all the articles using loops to find next and previous article. This step was repeated for each and every article. That's why it took so long. |
Thanks a ton! 😸 I'm running my webserver on a small ARM device, so with me it's not about 8 vs. 40 seconds, but 350 vs. 1300. The improvement of this patch for me is about a quarter of an hour! 👍 e.g.
|
Gosh! That's a huge number. My own blog is very small for now, that's why I never noticed it myself. The lesson I learned is to never put any sort of calculation in template 😄 |
It takes about 36s. Here is the top results of my profile run (which are not much different from Python 2.7):
The text was updated successfully, but these errors were encountered: