重负载和容量限制下的 Sharepoint 性能
我正在为一个包含大约 40 个应用程序的业务解决方案包开发一个新的存储系统。其中一些应用程序生成当前保存和组织在网络共享文件夹中的文档（主要是 docx，一些 pdf）。
应用程序平均每年生成约 150.000-200.000 个文档，这些文档应该以更加一致和可靠的形式保存（即单独的 SQL 数据库）。
Sharepoint 是一个领先的候选者，因为我们计划最终使用它的其他功能，除了 DMS 功能。我读过有关文档库限制的信息，即。每个文件夹有 2000 个文件，文档库的所有文件夹中最多有 1,000,000 个文件。 我还了解到可以绕过 2000 限制，但它会影响性能。我还没有发现在一个库中包含如此大量文件的真实体验。例如，如果我将文件夹限制增加到 50.000 会发生什么，这会对性能产生什么影响（通过 Web 服务读取/编辑/写入文档的请求变慢，尤其是在检查重复文件名、索引、搜索等时写入） .)。
一个重要的注意事项：如果没有必要，我们根本不会使用 sharepoint Web 门户，而是通过 Web 服务通过我们的应用程序完成所有操作，因此数据视图渲染速度较慢不是问题。
I'm working on a new storage system for a business solution package that consists of around 40 applications. Some of those applications generate documents (mostly docx, some pdf) that are currently saved and organized in a network share folder.
Applications generate about 150.000-200.000 documents a year in average, and those documents should be persisted in a more consistent and reliable form (ie. separate SQL database).
Sharepoint is a leading candidate, since we plan on using it's other features eventually, other then the DMS capabilities. I've read about document library limitations ie. 2000 files per folder with up to 1.000.000 files in all the folders of a document library.
I've also read that the 2000 limit can be bypassed BUT it affects performance. What I haven't found is the real world experience with such a large number of files in one library. And what will happen if I increase the folder limit to 50.000 for example, what impact would that have on performance (slower requests for reading/editing/writing documents through web services, especially writing if it checks for duplicate file names, indexing, searching etc.).
One important note: We will not be using sharepoint web portal at all if we don't have to, but instead do everything through our applications via web services, so data view slower rendering is not the issue.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可以在文档库中拥有任意数量的项目，只要您的最后一段是正确的（您不会通过门户本身访问信息）
我们对 DMS 系统进行了工作测试，在 上有 700 万个文件>相同文档库以及相同文件夹下。但我们永远不会通过门户查看该内容，我们使用 SPWeb.GetFile(guid) 方法使用这些文件，并且我们在另一个 SQL 数据库（存储文件的 GUID）上拥有与它们相关的所有信息
You can have as many items in a document library as you want, as long as your last paragraph is true (you wont access the information trough the portal itself)
We have a working test of our DMS system with 7 million files on the same document library and under the same folder too. But we never go trough the portal to see that content, we consume those files using the SPWeb.GetFile(guid) method, and we have all the information related to them on another SQL Database (which stores the GUID of the file)
2000 个限制不是硬性限制，它是列表视图中应显示的最大文件数量。
如果列表视图包含超过 2000 个项目，性能将开始下降。通过添加索引列并在列表上创建不超过 2000 个限制（给予或接受）的筛选附加视图，门户本身的使用仍然可以。
另外，请小心设置文件的权限。为每个文件提供自己的权限集也会降低性能，因为内部共享点将开始执行大量连接（在 SQL Server 中）以确定允许谁查看什么内容。
需要注意的是：非常非常好地规划您的基础设施。尤其是运行内容数据库的 SQL Server（集群）。
the 2000 limit is not a hard limit, it is the max amount of files that should be in a view on the list.
If a listview includes more than 2000 items performance will start to go down. By adding indexed columns and creating filtered additional views on a list that don't exceed that limit of 2000 (give or take), the use of the portal itself is still ok.
Also, be careful with setting permissions on the files. Giving each file it's own permission set will degrade performance also, seeing as internally sharepoint will start to perform massive joins (in sql server) to determine who is allowed to see what.
One note: plan your infrastructure very, very well. especially the sql server (cluster) the content database is running on.