Microsoft Sync Framework - 性能和可扩展性 [英] Microsoft Sync Framework - Performance and scalability

问题描述

我正在尝试在 SQL Server 数据库上使用 Microsoft Sync Framework 2.1.将有大量并发最终用户，与中央数据库服务器同步.

I am trying to use Microsoft Sync Framework 2.1 on a SQL Server database. There will be a high number of concurrent end users, synchronizing with a central database server.

进一步的规格是:

• 1500 个并发客户端连接到 1 个中央数据库服务器
  • 客户端使用的是 MS SQL Server Express 2008 R2
  • 服务器正在使用 MS SQL Server Enterprise 2008 R2

  有没有人有过类似这样的 Sync Framework 环境的经验?

  Does anyone have experience with Sync Framework environments similar to this?

  • 可能吗?
  • 在实施此计划时需要考虑哪些重要因素?
  • 我可以预期的身体限制是什么?

  推荐答案

  一些注意事项:

  1. 没有.范围 - 您可能希望为客户端到服务器保持 1 比 1 的范围比率，而不是针对一个服务器范围的 1500 个客户端范围.这将每个客户端的同步知识相互隔离，您甚至可以删除并重新创建客户端范围而不影响其他范围.同步知识也会非常紧凑.

  1. No. of scopes - you might want to keep a 1-to-1 scope ratio for client-to-server instead of 1500 client scopes against one server scope. this isolates the sync knowledge of each client from one another, you may even drop and recreate a client scope without affecting other scopes. sync knowledge will be much compact as well.

  范围定义 - 不要在一个范围内转储所有表.不同的表具有不同的特征(例如，仅下载、只读、更新频率较低、更新频繁等……).根据表格的特征对表格进行分组.

  Scope definition - dont dump all tables in one scope. different tables have different characteristics (e.g., download only, read-only, less frequent update, frequently updated, etc...). group tables based on their characteristics.

  批处理 - 如果更改很小，请不要批处理.您会在批处理中产生性能开销，因为批处理必须写入文件，稍后，它必须从文件重新构建更改数据集.

  Batching - if the changes are small, dont batch. you incur performance overhead in batching since the batching has to write files and later on, it has to reconstitute the change dataset from the files.

  元数据清理 - 设置元数据保留和元数据清理过程.这应该会减少同步元数据(跟踪表中的行和同步知识).

  Metadata Cleanup - setup metadata retention and metadata cleanup process. this should reduce the sync metadata (rows in the tracking tables and the sync knowledge).

  WCF 配置 - 注意您的 WCF 配置条目，例如超时、消息大小等...也请注意此问题:http://support.microsoft.com/kb/2567595

  WCF config -watch out for your WCF config entries such as timeout, message size, etc... be aware of this issue as well: http://support.microsoft.com/kb/2567595

  此外，请在此处查看其他范围注意事项:同步框架范围和 SQL Azure 数据同步数据集注意事项

  Also, have a look at other Scope considerations here: Sync Framework Scope and SQL Azure Data Sync Dataset Considerations

  这篇关于Microsoft Sync Framework - 性能和可扩展性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！