SharePoint Conference Notes on SharePoint 2010 – Day 3

2

Category : SharePoint 2010, SharePoint Conference

I am continuing my notes from the SharePoint Conference. Today I attended the Capacity and Performance Management, Externalizing BLOB Storage, and Advanced Development for Silverlight 3 in SharePoint sessions. I also did some hands on labs.

Link to my blog postings for each day at the conference.

 

 Capacity and Performance Management

  • Latency Improvements
    • Lighter and Faster pages
    • Early Rendering
    • WAN Optimizations
  • File Save Latency – this is a new feature that is used with Office 2010 documents and SharePoint 2010. Basically, you don’t see a save file dialog when saving large files. Instead, the file is saved to the local machine cache and incrementally uploaded to the SharePoint list. It should make for a great user experience in these situations.
  • Data Scale Improvements
    • 100 million items per search index (1 billion with FAST)
    • Tens of millions of documents/items in a single list
    • View/Query 5000 items at a time
  • Some of the 2007 limits stay the same
    • Site Collections per web application – 150,000
    • Site Collections per content database – 50,000
    • Content database size – 100 GB
  • Sharepoint Administrative Toolkit – new tools for capacity management. They didn’t give me too much details on this, so I am not sure if these are the exact names
    • Load Test Kit 2010
    • SPDiag 2010 – this is to do production monitoring
  • Logging is done in the database
    • Health data
    • Usage data
    • Gathers data across boxes through data providers
    • Extensible framework – we can build custom providers and custom reports
    • You can see the data through SQL Views, reports, Excel pointing at the SQL data, etc…
  • Different Server Architectures:
    • Single Server – for demos and dev boxes
    • Small Farm
      • around 500 users (~5 rps) and 50-100 GB of data
      • Usually 2 WFE/App Servers with a SQL cluster
      • App Servers can run on the WFE
    • Medium Farm
      • 10-50k users (~50rps) and 1-2 TB of data
      • Separating App Servers from WFE and scale out/load balancer both
    • Large Farm
      • 500k users (~500rps) and 10-20 TB of data
      • Lots of WFEs
      • Lots of App Servers
      • Lots of SQL Servers – probably 5TB per SQL box
      • Probably think about splitting your farms up if you have this situation
  • In medium or large environments, consider setting up a SQL Cluster for the content databases and a separate cluster for the logging and web analytics db. This was highly recommended.
  • Microsofts internal beta environment (this is probably larger than most organizations will need):
    • 3 General WFE
    •  1 WFE for dedicated search
    • 1 App Server for: Central Admin, User Profile Service, Metadata Management Service and Word Conversion Service
    • 2 App Servers for all the other services.
  • Recommended Server specifications:
    • 64 bit
    • WFE – Dual processor, 8 GB RAM
    • SQL Server – Quad Core, 16GB RAM

 

 Externalizing BLOB Storage – stores BLOB data separate from the Content DB on the file system

  • BLOBs typically account for 60-70% of total content in SharePoint
  • The official name for externalizing BLOB storage is: Remote BLOB Storage (RBS)
  • This is different from EBS (External BLOB storage), which was released in SharePoint 2007 SP1 and had issues: http://www.cleverworkarounds.com/2008/03/25/sharepoint-external-storage-api-crushing-my-dream/
  • Advantages over EBS:
    • Managed Interface
    • BLOB store scope = Content DB (verse the farm for EDS)
    • SharePoint UI = PowerShell
    • Number of Providers = Many (verse 1 for EDS)
  • Why use RBS?
    • Ability to group/store BLOBs separate from Metadata
    • Trade cost effective BLOB storage for expensive SQL storage
    • Storage management beyond SQL
  • A number of storage vendors are working with RBS – EMC, OpenText, AvePoint, Commvault, NetApp
  • RBS is a downloadable component in the SQL Server 2008 R2 Feature Pack
  • You can turn on RBS by a simple enable command in PowerShell and then the file gets stored on the file system
  • Install:
    • RBS Add in must be on SQL first
    • RBS and provider DLLs must be installed on all Web Front Ends
    • RBS must be enabled using PowerShell
  • BLOBs from SQL can be moved to RBS with a PowerShell commandlet
    • Migrates one BLOB at a time
    • You can terminate and resume the process
    • It is a live migration – no downtime required

 

Here are the Hands on labs I did today and my thoughts:

  • Business Intelligence - this lab dealt with Excel Services, Visio Services and PerformancePoint. I was really impressed with the new Visio Services. The Visio part of the lab started with an excel spreadsheet in a SharePoint document library. Then I opened Visio 2010. From there I could hook the data, from the excel spreadsheet, into Visio. Then I connected the data to my Visio objects. This example had a column in excel called status. If the status was 1, my server image in visio was green, if the status was 0, my server image in visio was red. After that I published the Visio diagram to SharePoint and it created a Visio Services diagram in my SharePoint site. So, I could view the Visio diagram in a web page. Then came the cool part – I edited my excel spreadsheet data (which was also in a SharePoint library) and it changed my Visio diagram automatically. This example was a quick way to show a server health dashboard controlled by excel data. But, I can think of lots of other possibilities for this new technology.

Comments (2)

[...] SharePoint Conference Notes on SharePoint 2010 – Day 3 (Greg Galipeau) [...]

Thank you for sharing your notes. I am attending a Sharepoint Conference this coming Sept. 23, 2010 in Denver where you’ll be able to attend workshops and technical classes – taught by Microsoft Certified Trainers, Microsoft engineers and Microsoft MVPs.

Post a comment