有序交付 BizTalk 性能
BizTalk 中发送端口上的“有序交付”是否有替代方案？消息的顺序对我来说非常重要，因此我创建了一个编排，当消息不按顺序时暂停消息，并在按顺序时恢复消息。我使用长时间运行的编排和直接端口绑定。
现在，某些消息在发送管道中处理得更快，因此有时消息会不按顺序排列（我使用文件适配器...）。 现在，当我检查“有序传递”时，无论如何，消息都是按顺序排列的，但性能确实非常糟糕（消息在发送端口中堆积起来），因此我需要在发送中找到有序传递的替代方案港口。
有什么建议吗？
谢谢
Is there an alternative to the "ordered delivery" on a send port in BizTalk? The sequence of the message is very important to me, so I created an orchestration that suspends the message when it is not in sequence, and resumes it when it is in sequence. I use a long running orchestration and direct port binding.
Now some messages are processed faster in the send pipeline, so it happens that sometimes the messages aren't in sequence (I use file adapter...).
Now when I check the "ordered delivery" the messages are in sequence no matter what, but the performance is really really bad (messages get bulked up in the send ports), so I need to find an alternative for the ordered delivery in the send port.
Any suggestions?
thx
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
现在，有序交付显然会增加 FIFO 模式的大量开销。请查看这篇文章，并查看第一期中的 FIFO 文章。另请查看 BizTalk 的总体性能，以帮助加快解决方案的其他一些方面的速度。现在，我看到一些人尝试通过 .net 和 SQL 订购他们自己的自定义解决方案，但性能并没有好多少，因为订购模式需要时间来处理。还可以看看这些关于性能的资源：
http://msdn2.microsoft.com/en-us/library/aa972201.aspx
http://msdn2.microsoft.com/en-us/library/aa972200.aspx
http://msdn2.microsoft.com/en-us/library/aa972198.aspx
设置 - http://msdn2.microsoft.com/en-us/library/ms864801 .aspx
Now ordered delivery does obviously add a lot of overhead with the FIFO pattern. Take a look at this article and look a the FIFO article in the first issue. Also take a look at BizTalk performance in general to help speed up some of the other areas on your solution. Now I've seen a few people try their own custom solution to ordering via .net and SQL and performance wasn't that much better because the ordering pattern takes time to process. ALso take a look at these resources around performance in general:
http://msdn2.microsoft.com/en-us/library/aa972201.aspx
http://msdn2.microsoft.com/en-us/library/aa972200.aspx
http://msdn2.microsoft.com/en-us/library/aa972198.aspx
setup - http://msdn2.microsoft.com/en-us/library/ms864801.aspx
您是否有多个数据发送到的位置？因此，它必须按顺序排列，但可以分开。如果是这样，您可以使用关联和有序交付，并使用多个管道来交付并加快流程。
Do you have multiple locations the data is being sent to? So, it has to be in sequence but could be partioned out. If so you can use correlation and ordered delivery and have several pipes that deliver and speed the process up.