使用 Workflow Foundation 的性能影响
我意识到这是一个非常普遍的问题，但我想知道在相当大的企业系统中使用 WF 相反命令式代码实现业务逻辑对性能的影响。 我想听听其他人在这方面的经验。
I realize this is a quite general question, but I am wondering about the performance impact of implementing business logic with WF contra imperative code in fairly large enterprise system. I would like to hear others experiences in this regard.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可以查看Windows Workflow Foundation 的性能特征，了解关键性能注意事项和建模在 Windows Workflow Foundation 上开发应用程序时非常重要的指南。
不过，我建议等待 PDC 上的 WF 4.0 公告（10 月底），因为 他们很有希望
编辑（PDC 之后，2008 年 11 月 11 日）：
好的，虽然 Kenny Wolf 在演讲中表示，从执行速度到持久性大小，性能提高了 10-100 倍。
此外，Rick Garibay 还发布了一些与 Kenny Wolf 的演讲后讨论
You can check Performance Characteristics of Windows Workflow Foundation for key performance considerations and modeling guidelines that are important when developing applications on top of the Windows Workflow Foundation.
However I would suggest to wait for the WF 4.0 announcement at PDC (end of October) since they are promising
EDIT (after PDC, 11Nov08):
OK, not much revealed about performance at PDC, although Kenny Wolf said in his talk that there are 10-100X performance improvements from execution speed to persistence sizes.
Moreover, Rick Garibay posted some post-talk discussions with Kenny Wolf here. I am copying a relevant passage:
我曾经做过一些关于 WF 性能的基准测试。 事实证明“声明条件”相当慢。 我相信这是由于在这个过程中进行了很多反思。
I once did some benchmark about WF performance. It turns out that "declarative condition" is pretty slow. I believe that it is due to a lot of reflection is done in the process.