Partials are slow in dust.js

[giridharkn]

Dust.js is best template engine....in my case much need of partials but as per linked in benchmark handlebars are good at partials.

http://linkedin.github.io/dustjs/benchmark/index.html

Please help me...

[jimmyhchan]

Performance is very important to this project, but we are finishing a few feature requests before getting back to perf improvements.

[prashn64]

Added a milestone for performance. We will get to it after either the 2.4 milestone or enhancing parameter passing.

[xjamundx]

I'm finding significant issue with performance when rendering templates with large numbers of partials. In some cases these take 1-3 seconds to render. Most of the time appears spent inside the clone function.

[rragan]

With the exception of path.js, those are all related to compiling dust templates to Javascript. If you are in a dev environment editing templates and hitting refresh a lot, then compiling on every run might make sense. For production use, you ought to compile to JS once and only execute the compiled JS.

[xjamundx]

Right and replacing (manually) the lines of the clone command in the compiled parser.js file with the folowing makes it work significantly faster (hat tip to @totherik):

function clone(object) {
    return {
        offset: object.offset,
        line: object.line,
        column: object.column,
        seenCR: object.seenCR
    };
}

[sethkinast]

#497 uses a new version of the parser that no longer performs clone()

[maciejkowalski]

This should be closed, there is already a fix for that in #497