|
|
|
|
|
by stdbrouw
4169 days ago
|
|
I have my own little blogging engine based on https://github.com/debrouwere/render and what I've found is that the bottleneck is almost always IO. Rendering templates is so fast it simply does not matter whether you run it on a gazillion cores or not. Getting data from disk and then writing it to disk means you're dealing with contention, where parallelizing stuff can actually make it slower. So it can actually make sense to do all of this serially. But of course, that doesn't mean you can't do incremental rebuilds. If the data is older than both the HTML and the template, then there's no need to rerender. More generators should support this, either internally or by making it easier to run them as part of a Make build. |
|