Hi everyone! I work as a .NET developer and recently (VERY recently ) I develop various Sharepoint features. However, I received the following mail from aMOSS 2007 user:"The system [Sharepoint] works slowly, first logging lasts long, it freezes when opening a new [Sharepoint] site, and sometimes while uploading documents the system halts and doesn't even allow to browse sites. There is no rule regarding the time when it happens."So, I have to take care of server's performance. And my question is: how can I test it? What are the best ways for an administrator to test performance of a Sharepoint server? I have no idea what to start with as I have no Sharepoint administration skills (well, no administration skills whatsoever)Please don't mind my English, as you probably noticed it's not my native language

You can test a SharePoint server just like you would with a typical web server. I would have a look at Performance counters in windows 2003. Key ones to test are: % Processor time - Shows the percentage of elapsed time that this thread used the processor to execute instructions % Memory utilisation - Shows the average utilisation of system memory for the application pool. You need to identify the correct application pool to monitor. Monitor these on the web server and the database server while the user performs the actions. It maybe that you servers are under spec'd or that there is a bottle neck. Hope this helps Dave

Sounds like you may be recycling your AppPools nightly or daily. This is perfectly acceptable and recommended but the first user that hits a site will experience this slowness and the reason is because that user unfortunitly making that first connection to SQL after the recycle. We recomend placing the Warm Up script in place to run after your scheduled App Pool recycles. You can find a reference to this on Joel Oleson's blog or on the Sharepoint Team Blog. Hope this solves your issues.

We were having similar problems like the site will freeze while uploading documents or opening itself. There could be several reasons for this: * Network Contention, use httpwatch like tool to figure this out * Try accessing the site from server itself * Memory and processor consumption on server should be less the 60% on an average. * look for w3wp memory in task manager * enable blob cache and http compression and so on as indicated in below link article to increase the performance http://celerity12.blogspot.com/2010/04/httpcompression-and-browser-caching.html Thanks