设计 WCF 服务器以实现低延迟
如何实现WCF服务器在发布订阅场景下的低延迟？具体来说，客户端订阅数据并接收更新，所讨论的延迟是在数据更改和客户端接收更改之间？ CPU、内存、带宽要求并不重要，而且可能很高。
基础知识很明显：二进制序列化、命名管道等。但是，例如，通过始终连接的流发送数据有意义吗？或者将批量更新作为单个消息发送以减少 RPC/标头开销？
可能有一些带有代码或接口的项目可以用作示例？
How to achieve low latency of WCF server in publish-subscribe scenario? Specifically, clients subscribe to data and receive updates, latency in question is between data changing and client receiving the change? CPU, memory, bandwidth requirements are not important and can be high.
Basics are obvious: binary serialization, named pipes, etc. But does it makes sense, for example, to send data through always-connected stream? Or to send batch of updates as a single message to decrease RPC/header overhead?
May be there are some projects with code or interfaces available to use as example?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这不是一个全面的解决方案，但是：要减少与数据大小和网络传输速度相关的延迟，您可以使用 google 协议buffers 通过网络压缩数据。 GitHub 项目位于此处。
Not a comprehensive solution but: To reduce latency associated with size of data and network transfer speeds you could use google protocol buffers to compress your data over the wire. GitHub projects is here.
如果您使用双工通道，则可以让客户端连接到服务器，并在此过程中传递另一个服务协定作为回调。然后，服务器使用此回调将更新发送到客户端（当更新可用时）。
我已经使用这种方法编写了一个内部发布-订阅机制，并且延迟大约与您通过 WCF 所期望的一样低。
您的目标绩效是什么？
这篇 MSDN 文章讨论如何使用 WCF 双工通道。
If you use a duplex channel, you can have clients connect to the server and in doing so pass another service contract as a callback. The server then uses this callback to send updates to the client as they become available.
I've written an in-house pub-sub mechanism using this approach and latency is about as low as you would expect possible via WCF.
What is your target performance?
This MSDN article discusses using a WCF duplex channel.
您是否看过
http://geekswithblogs.net/BVeldhoen/archive/2008/01/26/wcf-latency-test-harness.aspx
它考虑了各种绑定和数据尺寸。
Have you looked at
http://geekswithblogs.net/BVeldhoen/archive/2008/01/26/wcf-latency-test-harness.aspx
It takes into account various bindings, and data sizes.