jase@sharepointlonghorn.com@sharepointlhornseb@appcogs.com@sebmatthews
SharePoint Foundation Loggerhttp://spflogger.codeplex.comTwitter: @sharepointlhornLinkedIn:www.linkedin.com/in/jasonhimmel...
Seb
Developer or Evaluation environmentsCPU: 4 cores, 64-bit requiredRAM: 4GBHard Drive space: 80GBProduction in Single Server...
 Close location of Vservers
 Budget constrained failover options
 Loss of minimum 8% compute for overhead Clustering complications
 Instant file initialization
DB Files RAID Level Optimization1 TempDB data 10 Write2 TempDB logs 10 Write3 ContentDB data 10 ReadWrite4 ContentDB logs ...
http://www.sharepointlonghorn.com http://spflogger.codeplex.comhttp://www.sebmatthews.nethttp://www.sharepointpromag.com/c...
http://spflogger.codeplex.comwww.sentri.comwww.sharepointlonghorn.com@sharepointlhornwww.linkedin.com/in/jasonhimmelsteinh...
Seb Matthews+44(0)7765 090308seb@appcogs.com@sebmatthews http://sebmatthews.nethttp://linkedin.com/in/sebmatthews
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
SharePoint Performance:Best Practices from the Field - SPSBoston 2013
Upcoming SlideShare
Loading in...5
×

SharePoint Performance:Best Practices from the Field - SPSBoston 2013

739

Published on

Want to avoid the performance mistakes before you make them? This in-depth session we will discuss how to properly position your SharePoint farm for success beginning with "hardware" and ending with troubleshooting methodologies to maximize performance. Find the pitfalls before you hit them from someone who has climbed out of the deep dark holes in the wild. Best Practices from the Field combines recommendations from Microsoft with the experience of trial & error.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
739
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
39
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SharePoint Performance:Best Practices from the Field - SPSBoston 2013

  1. 1. jase@sharepointlonghorn.com@sharepointlhornseb@appcogs.com@sebmatthews
  2. 2. SharePoint Foundation Loggerhttp://spflogger.codeplex.comTwitter: @sharepointlhornLinkedIn:www.linkedin.com/in/jasonhimmelsteinBlog:www.sharepointlonghorn.comMicrosoft vTSPvirtual Technology Solutions Professionalwww.sharepointlonghorn.comhttp://bit.ly/SharePointBIJasonhttp://spflogger.codeplex.com
  3. 3. Seb
  4. 4. Developer or Evaluation environmentsCPU: 4 cores, 64-bit requiredRAM: 4GBHard Drive space: 80GBProduction in Single Server or farmenvironmentsCPU: 4 cores, 64-bit requiredRAM: 8GBHard Drive space: 80GBSmall FarmCPU: 4 cores, 64-bit requiredRAM: 8GBHard Drive space: 80GBMedium FarmCPU: 8 cores, 64-bit requiredRAM: 16GBHard Drive space: 80GBLarge FarmUp to 2TB Content DBSRAM: 32 GBFrom 2TB to 5TB Content DBSRAM: 64 GB
  5. 5.  Close location of Vservers
  6. 6.  Budget constrained failover options
  7. 7.  Loss of minimum 8% compute for overhead Clustering complications
  8. 8.  Instant file initialization
  9. 9. DB Files RAID Level Optimization1 TempDB data 10 Write2 TempDB logs 10 Write3 ContentDB data 10 ReadWrite4 ContentDB logs 10 Write5 Crawl DB logs 10 Write6 Crawl DB data 10 ReadWrite7 Property DB logs 10 Write8 Property DB data 10 Write9 Services DB logs 10 Write10 Services DB data 5/10 ReadWrite11 Archive Content DB 5 Read12 Publishing Site Content DB 5 Read
  10. 10. http://www.sharepointlonghorn.com http://spflogger.codeplex.comhttp://www.sebmatthews.nethttp://www.sharepointpromag.com/content1/topic/sharepoint-performance-troubleshooting-141506/catpath/sharepoint-server-2010http://www.sharepointcowboy.comhttp://technet.microsoft.com/en-us/library/cc262485.aspxhttp://technet.microsoft.com/en-us/library/cc262787.aspxhttp://technet.microsoft.com/en-us/library/ff758647.aspxhttp://technet.microsoft.com/en-us/library/ff758645.aspxhttp://technet.microsoft.com/en-us/library/ff758659.aspxhttp://technet.microsoft.com/en-us/library/cc298801.aspxhttp://technet.microsoft.com/en-us/library/cc261716.aspxhttp://technet.microsoft.com/en-us/library/ff758658.aspxhttp://technet.microsoft.com/en-us/library/ff758659.aspxhttp://technet.microsoft.com/en-us/library/ff823731.aspxhttp://www.iis.net/community/default.aspx?tabid=34&g=6&i=1466
  11. 11. http://spflogger.codeplex.comwww.sentri.comwww.sharepointlonghorn.com@sharepointlhornwww.linkedin.com/in/jasonhimmelsteinhttp://bit.ly/sharepointbi
  12. 12. Seb Matthews+44(0)7765 090308seb@appcogs.com@sebmatthews http://sebmatthews.nethttp://linkedin.com/in/sebmatthews
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×