在Windows工作流基础Statemachines适用于高性能的情景？ [英] Are Windows Workflow Foundation Statemachines suitable for high performance scenarios?

问题描述

i'm目前正在处理一个系统，如果我必须跟踪状态并行几千对象发送可能的状态每分钟更新几次。此外，我必须执行额外的计算（不慢的IO的东西，只是用CPU）。

i´m currently dealing with a system where i have to track the state for several thousand objects in parallel that send possible state updates a few times every minute. In addition i have to perform additional computation (no slow IO stuff, just using CPU).

我目前使用的是自定义的状态机实现。但是，由于WF是在系统的其他部分中使用的，我不知道如果WF状态machine's可能适用于极少数这样的情况下（小于5）。状态

I currently use a custom state machine implementation. however, as WF is used within other parts of the system, i wonder if the WF state machine´s may be suitable for such a scenario with a handful (<5) of states.

我担心，当它涉及到性能开销可能会太大。由于MS文档并没有真正涵盖关于为WF状态机性能的话题，我不知道，如果一些SO成员都有regaring WF状态机性能的一些信息或资源？

I fear that the overhead might be too big when it comes to performance. As the MS documentation does not really cover topics regarding performance for WF state machines, i wonder if some SO member has some information or resources regaring WF state machine performance?

关于
学家

推荐答案

状态机是非常适合高性能系统。如果你真的使用Workflow Foundation的需要非常高的性能增添了不少的复杂性和开销。我发现的BizTalk是完全不适合非常高的性能。

State machines are great for a high performance system. If you really need very high performance using workflow foundation adds a lot of complexity and overhead. I've found biztalk to be totally unsuitable for very high performance.

这篇关于在Windows工作流基础Statemachines适用于高性能的情景？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！