blocks|key|118646|text|因为最后，Smarty会将模板文件编译并缓存为原生PHP代码，所以在理论上确实没有性能差异。当然，由于每次都需要解释的Smarty代码块，总是会有一些性能损失。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|118647|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Because in the end, Smarty compiles and caches the templates files to native PHP-code, there is indeed no theoretical performance difference.
Of course there will always be some performance loss due to the chunk of Smarty-code that needs to be interpreted every time.

blocks|key|118888|text|您可能还想使用一个与Smarty类似的新模板库，名为Dwoo|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|118889|entityMap|0|LINK|mutability|MUTABLE|url|http://dwoo.org/^0|Q|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You might also want to take at a new template library that is similar to Smarty called <a href="http://dwoo.org" rel="nofollow noreferrer">Dwoo</a>

blocks|key|118593|text|只是发现this非常简单的基准测试-可能不是很重要。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|118594|entityMap|0|LINK|mutability|MUTABLE|url|http://lutt.se/blog/2006/08/13/why-template-engines-like-smarty-sucks-in-php.html^0|4|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Just found <a href="http://lutt.se/blog/2006/08/13/why-template-engines-like-smarty-sucks-in-php.html" rel="nofollow noreferrer">this</a> very simple benchmark - propably not very significant.

blocks|key|118979|text|这是另一个模板解决方案XSLT这里是我对我转换的一个页面(它是一个简单的页面)的基准测试：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|118980|//+with+smarty+(baseline)
++++0.014+seconds

//+with+xsl/xslt-clientside
++++0.008+seconds
++++42%25+decrease+in+server+stress

//+with+xsl/xslt-serverside
//+this+process+would+only+be+done+if+the+users+browser+doesn't+support+client-side+XSLT
++++0.016+seconds
++++14%25+increase+in+server+stress|code-block|syntax|javascript|118981|它并不适合每个人，但如果性能是您主要关心的:)|118982|最重要的是，您允许客户端缓存您的模板。|118983|下面是我正在做的一个例子(这是我的一个站点)：http://pixao.com|offset|length|118984|这是一个更大规模的网站上的另一个例子：http://worldofwarcraft.com|118985|到目前为止，我还没有遇到过任何阻碍演出的人。|118986|entityMap|0|LINK|mutability|MUTABLE|url|http://pixao.com/|1|http://worldofwarcraft.com/^0|0|0|0|0|N|G|0|0|J|Q|1|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@$M|17|N|18|1|19]]|A|$]]|$1|O|3|P|5|6|7|1A|8|@]|9|@$M|1B|N|1C|1|1D]]|A|$]]|$1|Q|3|R|5|6|7|1E|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]]]

here's another templating solution XSLT here are my benchmarks for one of the pages i converted (its a simple page):

<pre><code>// with smarty (baseline)
 0.014 seconds

// with xsl/xslt-clientside
 0.008 seconds
 42% decrease in server stress

// with xsl/xslt-serverside
// this process would only be done if the users browser doesn't support client-side XSLT
 0.016 seconds
 14% increase in server stress
</code></pre>

Its not for everyone but if performance is your main concern :)

On top of that you allow the client to cache your template.

here's an example of what I'm doing (this is one of my sites): <a href="http://pixao.com" rel="nofollow noreferrer">http://pixao.com</a>

and here's another example of it on a larger scale site: <a href="http://worldofwarcraft.com" rel="nofollow noreferrer">http://worldofwarcraft.com</a>

so far i have yet to run into any show stoppers

blocks|key|921695|text|下面是一个模板引擎基准测试，测试PHP和更多的模板引擎http://www.raintpl.com/PHP-Template-Engines-Speed-Test/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|921696|921697|For+assignment+Twig更快，它将html模板编译成类，所以它在执行更多内容时也比PHP+include更快！我是重的(许多文件)和复杂的，但非常快！|unordered-list-item|921698|循环越快是PHP包含，很快就会有雨，这是非常容易，小(1个文件)和快速。|921699|921700|entityMap|0|LINK|mutability|MUTABLE|url|http://www.raintpl.com/PHP-Template-Engines-Speed-Test/^0|R|1J|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|-4|5|6|7|W|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|X|8|@]|9|@]|C|$]]|$1|H|3|I|5|G|7|Y|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

Here a template engine benchmark that tests PHP vs Smarty and many more template engines <a href="http://www.raintpl.com/PHP-Template-Engines-Speed-Test/" rel="nofollow">http://www.raintpl.com/PHP-Template-Engines-Speed-Test/</a>

<ul>
<li>For assignment Twig is the faster, it compile the html template to a classes, so it's also 
faster in executing more than the PHP include! IMHO is heavy (many files) and complicate, but is very fast!</li>
<li>For looping the faster is the PHP include, and soon after there's Rain which is very easy, small (1 file) and fast.</li>
</ul>

blocks|key|3336686|text|Smarty会在第一次使用所有模板文件时为它们生成PHP代码，前提是您已经正确设置了它们，并在可能的情况下使用它们，而不是再次解析模板。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3336687|我用了一段时间，它足够快了，但最后我把它换成了普通的PHP文件，因为它有一点限制(太多PHP4-isms)。|3336688|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Smarty generates PHP code for all its template files when they're first used, provided you have it set up correctly, and uses them when possible instead of parsing the templates again.

I used it for a while and it was fast enough, but in the end I swapped it out for plain PHP files because it was a bit limiting (too many PHP4-isms).

blocks|key|118742|text|Smarty本身就是一个相当大的库。如果你打算使用Smarty，我建议你使用APC来缓存编译后的版本。它将抵消相当大的Smarty库的大小...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|118743|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Smarty itself is rather a large library... If your going to use Smarty, I suggest you use APC to cache the compiled version.. It will offset the rather large size of the Smarty library...

blocks|key|4182188|text|这取决于您如何使用Smarty，因为页面的流程可能会改变(|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4182189|经典的纯PHP流程：|4182190|4182191|Output|unordered-list-item|4182192|Handle+data|4182193|4182194|Handle+queries|4182195|4182196|Handle+data|4182197|4182198|...|4182199|+$_REQUEST+$_REQUEST数据库|4182200|经典的Smarty流程：|4182201|4182202|Handle+all+$_REQUEST+data|4182203|Handle+all+$_REQUEST|4182204|+all|4182205|如果简单的PHP在这个页面上花费了1.0秒，那么Smarty页面也需要1.0秒。但是如果我们假设所有的数据库和$_request处理都需要0.7秒。普通的PHP直接开始输出，而Smarty版本在0.7秒后开始输出。因此，浏览器可以更快地开始下载样式表和图像。无输出也意味着“停止”按钮无效。|4182206|但是，在Smarty中，您可以从模板中调用函数和方法。将慢的部分延迟到需要数据的地方。|4182207|entityMap^0|K|9|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1G|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|1I|8|@]|D|@]|E|$]]|$1|L|3|M|5|K|7|1J|8|@]|D|@]|E|$]]|$1|N|3|J|5|K|7|1K|8|@]|D|@]|E|$]]|$1|O|3|P|5|K|7|1L|8|@]|D|@]|E|$]]|$1|Q|3|J|5|K|7|1M|8|@]|D|@]|E|$]]|$1|R|3|S|5|K|7|1N|8|@]|D|@]|E|$]]|$1|T|3|J|5|K|7|1O|8|@]|D|@]|E|$]]|$1|U|3|V|5|K|7|1P|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1R|8|@]|D|@]|E|$]]|$1|10|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]|$1|11|3|12|5|K|7|1T|8|@]|D|@]|E|$]]|$1|13|3|14|5|K|7|1U|8|@]|D|@]|E|$]]|$1|15|3|16|5|6|7|1V|8|@]|D|@]|E|$]]|$1|17|3|18|5|6|7|1W|8|@]|D|@]|E|$]]|$1|19|3|1A|5|6|7|1X|8|@]|D|@]|E|$]]|$1|1B|3|-4|5|6|7|1Y|8|@]|D|@]|E|$]]]|1C|$]]

It depends on how you use Smarty because the flow of your pages can change

Classic plain PHP flow:

<ul>
<li>Output</li>
<li>Handle $_REQUEST data</li>
<li>Output</li>
<li>Handle database queries</li>
<li>Output</li>
<li>Handle $_REQUEST data</li>
<li>Output</li>
<li>...</li>
</ul>

Classic Smarty flow:

<ul>
<li>Handle all $_REQUEST data</li>
<li>Handle all database queries</li>
<li>Output all</li>
</ul>

If plain PHP took 1.0 sec for this page the Smarty page also takes 1.0 sec. BUT if we assume that all database and $_request handeling takes 0.7 sec. The plain PHP starts output directly while the Smarty version starts outputing after 0.7 sec. Therefor the browser can start downloading stylesheets and images faster.
No output also means the "Stop" button has no effect.

However in Smarty you can call functions and methods from within the template.
Delaying the slow part to where the data is needed.

blocks|key|4182247|text|还有a+drop+in+replacement+for+Smarty+called+Template+Lite，它在库文件大小方面要轻量级得多。也就是说，我已经在一些非常高负载的情况下使用了原始的Smarty，而不需要在这个库中进行交换。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4182248|entityMap|0|LINK|mutability|MUTABLE|url|http://templatelite.sourceforge.net/^0|2|1H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There is <a href="http://templatelite.sourceforge.net/" rel="nofollow noreferrer">a drop in replacement for Smarty called Template Lite</a> which is much more lightweight in respect to the library file size. That said, I have used the original Smarty in some extremely high load situations without needing to swap in this library.

blocks|key|3336922|text|根据我自己的经验和非正式的基准测试，Smarty本身不会导致任何重大的性能下降。然而，当你开始编写定制插件时，事情就开始走下坡路了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3336923|Smarty模板被编译和缓存为PHP，但自定义插件总是在运行时加载和执行，并且总是比在普通的旧PHP文件中运行相同的代码慢。在自定义字符串格式化插件中，您不会注意到这一点，但是当您在插件中执行数据库查询时，您肯定会看到它。|3336924|总的来说，我强烈推荐Smarty。从PHP中获得显示使我们的代码更具可读性和可维护性。你只需要确保你对你放在插件中的东西很小心。|3336925|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Based on my own experiences and informal benchmarks, Smarty doesn't by itself cause any major performance reductions. However, when you get into writing custom plugins, things go downhill. 

A Smarty template is compiled &amp; cached as PHP, but a custom plugin is always loaded and executed at runtime and is always slower than running the same code in a plain old PHP file. You're not going to notice this too much with a custom string formatting plugin, but you'll definitely see it when doing database queries in a plugin.

Overall, I highly recommend Smarty. Getting the display out of the PHP has made our code so much more readable and maintainable. You just have to make sure you're careful about what you put in plugins.

I am considering Smarty as my web app templating solution, and I am now concerned with its performance against plain PHP. 

The Smarty site says it should be the same, however, I was not able to find anyone doing real benchmarking to prove the statement right or wrong.

Did anyone do some benchmarking of Smarty vs plain PHP? Or maybe come across some resources on such tests?

Thanks

Smarty benchmark, anyone?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在考虑将Smarty作为我的web应用模板解决方案，我现在关心的是它在与普通PHP的对比中的性能。Smarty网站说应该是一样的，然而，我找不到任何人做真正的基准测试来证明这一说法是正确的还是错误的。有人做过Smarty和普通PHP的基准测试吗？或者可能会遇到一些关于这类测试的资源？谢谢

问Smarty benchmark，有人知道吗？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Smarty benchmark，有人知道吗？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Smarty benchmark，有人知道吗？
EN