Quantcast
Viewing all articles
Browse latest Browse all 21070

Effective Storage Mechanism of a Document Repository Site

Hi Team,

We have a MOSS application that is built in WSS3.0/MOSS 2007 and is a document repository system.
On a daily basis large number of documents are uploaded to this MOSS Site. The documents are stored into the Content Database after fulfilling some criteria. Below are the Content Databases.

Content Database A
Content Database B
Content Database C
Content Database D
Content Database E

Since, each of them have exceeded the Microsoft specified limit of 100GB, secondary data files have been added and thus each of the above databases currently store data till 325GB and is increasing by 2GB on a monthly basis.

Questions
1) At the rate the data is being uploaded it will break the 400GB maximum limit. Is this adviceable storage mechanism?
2) Is performing a migration to SharePoint 2013(or 2010) a better option than adding Second Generation Content Databases?
3) Offlate, users are reporting performance issues and when a PAL report was generated it highlighted some critical warnings. Do they suggest database issues or any performance issues? If so, how to tune them?
4) Any whitepapers/documents available to find exact resolution to the critical warnings generated in the PAL report?

PAL Report Critical Warnings

1)Less than 5 percent of RAM is available or less than 64MBs of RAM is available

2)Greater than 25ms physical disk READ response times

3)Less than 500 MB of free disk space

4)More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec

5)Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour

6)More than 80% Processor Utilization

7)Greater than 25ms logical disk WRITE response times

8)Page life expectancy is less then 5 minutes

9)More than 30% privileged (kernel) mode CPU usage

10)Possible Memory Leak: More than 500MBs between overall Min and overall Max and an increasing trend of more than 100MBs per hour

11)Greater than 25ms logical disk READ response times

12)Greater than 25ms physical disk WRITE response times

13)ASP.NET execution times are greater than 8 seconds

14)An increasing trend of more than 10MBs per hour in .NET CLR Memory

15)More than 10 ready threads are queued for each processor

16)More than 50 .NET CLR Exceptions Thrown / sec

I have already checked the below references to analyze the PAL reports.

References
http://www.petri.co.il/analyze-windows-performance-logs.htm
http://www.petri.co.il/performance-analysis-of-logs-reports.htm
http://msdn.microsoft.com/en-us/library/cc296652.aspx
http://windowsitpro.com/systems-management/get-handle-windows-performance-analysis
http://bradmcgehee.com/2008/12/23/check-out-the-free-performance-analysis-of-logs-pal-tool/
http://blogs.technet.com/b/clint_huffman/archive/2008/09/02/how-to-use-the-pal-tool-for-biztalk-performance-analysis.aspx
http://danieladeniji.wordpress.com/2010/03/04/microsoft-performance-analysis-of-logs-pal-tool/
http://vmtoday.com/scripts-free-tools/view-pal/vmware-view-pal-connection-server-sample-report/?replytocom=8

Any help will be deeply appreciated.

Thanks,
Bhargav


Bhargav Reddy


Viewing all articles
Browse latest Browse all 21070

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>