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

testing: Add some site build benchmarks #3535

Closed
bep opened this Issue May 29, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@bep
Member

bep commented May 29, 2017

I'm pondering with the nested sections implementation now and then, and I'm about to add a new data structure to Hugo that is needed by the sections handling, but may also speed up other parts of Hugo.

But then it would be great to have some controlled benchmarks to compare with.

Nothing fancy to begin with, variations on these:

  • Number of regular pages; 10, 100, 500, 1000, 5000, 30000
  • Number of tags
  • Number of tags per page
  • Number of root sections
  • Shortcodes ...

@bep bep added the Enhancement label May 29, 2017

@bep bep self-assigned this May 29, 2017

bep added a commit to bep/hugo that referenced this issue May 30, 2017

hugolib: Add site building benchmarks
To run a subset of these benchmark, one can do something like this:

```
go test -run="NONE" -bench="BenchmarkSiteBuilding/tags_per_page=0.*shortcodes=true.*render=false"  -test.benchmem=true ./hugolib
```

Which will run without any tags, with shortcodes, but will skip rendering.

Fixes #3535

@bep bep closed this in #3540 May 30, 2017

bep added a commit that referenced this issue May 30, 2017

hugolib: Add site building benchmarks
To run a subset of these benchmark, one can do something like this:

```
go test -run="NONE" -bench="BenchmarkSiteBuilding/tags_per_page=0.*shortcodes=true.*render=false"  -test.benchmem=true ./hugolib
```

Which will run without any tags, with shortcodes, but will skip rendering.

Fixes #3535

@ghost ghost referenced this issue Jun 12, 2017

Open

spf13/hugo v0.22 released #11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment