is golang html template slow?

<p>Hello, </p> <p>go newbie here. So I am reading the posts below and I&#39;m super surprised by it. A year later, is the use of reflection that causes slowness still a thing in latest version?</p> <p><a href="http://stackoverflow.com/questions/31361745/slow-performance-of-html-template-in-go-lang-any-workaround" rel="nofollow">http://stackoverflow.com/questions/31361745/slow-performance-of-html-template-in-go-lang-any-workaround</a></p> <p><a href="https://www.reddit.com/r/golang/comments/3d6j42/why_is_htmltemplate_so_slow/" rel="nofollow">https://www.reddit.com/r/golang/comments/3d6j42/why_is_htmltemplate_so_slow/</a></p> <hr/>**评论：**<br/><br/>Sphax: <pre><p>Just use html/template and worry about its performance when it&#39;s becoming a problem. </p></pre>MrCowPie: <pre><p>i can&#39;t agree more. This post is more for my curiosity than anything else. </p></pre>Sphax: <pre><p>well html/template still uses reflection and as far as I know there hasn&#39;t been gigantic speed improvements in the reflect package. in one year we got global speed improvements though with go 1.6 and 1.5 so there&#39;s that. </p> <p>unfortunately I don&#39;t have experience at high volume using html/template so I can&#39;t give you figures. I do use encoding/json which is reflection heavy on a bunch of micro services with a bit of traffic and from the profiling I&#39;ve done it&#39;s rarely the bottleneck. </p></pre>: <pre><p>[deleted]</p></pre>valyala: <pre><p>Actually, there are much faster dynamic template engines without Go gen exist - see <a href="https://github.com/CloudyKit/jet" rel="nofollow">jet</a> as an example.</p></pre>GoTheFuckToBed: <pre><p>just do it</p></pre>MrCowPie: <pre><p>researching is part of doing. </p></pre>xrstf: <pre><blockquote> <p>&#34;One good test is worth a thousand expert opinions.&#34;</p> <p>(Wernher von Braun)</p> </blockquote></pre>MrCowPie: <pre><p>noted and tested. with a database connection and simple select statement, go is about 3-4x faster than php</p></pre>runicnet: <pre><p>sounds like procrastination, </p></pre>tscs37: <pre><p>the template package still uses a lot of reflection, not as fast as it could be.</p> <p>The best method would be to setup a database with expected latencies and test if the time it takes the page to render actually impacts the performance significantly, chances are the DB connection will be slower.</p> <p>Secondly, you could design the template render as a standalone static server to serve these templates, thusly you can more easily scale them upwards by just adding more of them (aka microservices)</p> <p>Lastly, you could try to design a SPA instead, that requires to render a template at worst once instead of many pages, the backend then uses an API to communicate.</p></pre>MrCowPie: <pre><p>well I don&#39;t know if the html template is as slow as said in the link posted above but I took your advice and tested with a database connection. The code will print out a resultset of about 20 strings to the html page. For comparison, I wrote a similar code using php7 with opcode caching enabled. Unless I&#39;m doing something wrong, golang is about 3-4x faster in my test.</p></pre>tscs37: <pre><p>That sounds about reasonable.</p> <p>The PHP7 code is fully interpreted while Go only needs to interprete and reflect on the template code, which should slow it down a bit but the rest gives it sufficient boost over PHP.</p></pre>drvd: <pre><p>Slow compared to what?</p> <p>&#34;Is 2m short?&#34; is a useless question: 2m ist huge for amoeba and tiny for stars. </p></pre>