Quando usa coleções do site vs subsites afetam o desempenho?

Question

Minha topologia atualmente planejada é uma coleção de sites com 80 subsites, 1.600 páginas, 50 - 100 GB de dados e 165 grupos de segurança.

Estou considerando quebrar os subsites em 8 coleções diferentes do site com seu próprio banco de dados de conteúdo no mesmo cluster do SQL Server.

Devem realizar qualquer benefício de desempenho fora do Backup DB e do tempo de restauração?

Answer 1

You're within the limitations of SharePoint (http://technet.microsoft.com/en-us/library/cc262787.aspx) in either scenario, which is good. Some of my thoughts

As far as performance, I don't think you'll see much in way of improvement going from one DB to multiple DBs, unless you can move the DB files to different disk arrays.

100GB is a reasonable size for one DB. MS recommends 200GB max, but the recommendation is for management of the dbs (harder to backup/restore, times get longer)

Using unique site collections also bring along some features or headaches, depending on what you require

• Unique permissions
• Unique quotas
• Roll up data is tougher (especially on SP2010)
• Unique DBs
• No central navigation (unless you use managed metadata)

And there's more in a post I wrote a while back: http://sp365.co.uk/2012/01/initial-topology-planning-site-collections-vs-subsites/

HTH, let me know if you have further questions

Answer 2

You might also take into account that the initially required storage capacity will grow over time. Having to split your "catch-all" SiteCollection later on won't be fun, so my recommendation is to start with several SiteCollections and have room for growth