Developer Dashboard

Good article here
http://blogs.msdn.com/b/russmax/archive/2010/02/10/sharepoint-2010-logging-improvements-part-2-introducing-developer-dashboard.aspx

Good article here for devs
http://www.sharepoint4developers.net/en-nz/post/sharepoint-2010-developer-dashboard.aspx

Todd on Developer Dashboard
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=189

Monitoring SharePoint 2010 Performance and the Developer Dashboard
http://sharepoint.microsoft.com/Blogs/GetThePoint/Lists/Posts/Post.aspx?ID=457

Why SharePoint 2010 Developer Dashboard Is For All IT Professionals
http://blogs.msdn.com/b/chrisfie/archive/2010/01/29/why-sharepoint-2010-developer-dashboard-is-for-all-it-professionals.aspx

Bill Baer’s take on Developer Dashboard
http://blogs.technet.com/b/wbaer/archive/2009/11/21/welcome-to-the-developer-dashboard.aspx

Special Project - http://blogs.msdn.com/b/tejasr/archive/2011/07/01/sharepoint-2010-performance-dashboard-server-performance-reporting-post-1.aspx

QUICK NOTE: Although you can control Developer Dashboard with PowerShell to get more control an easy fast solution is to just use site?developerdashboard=true in your URL after your turn the developer dashboard on.

More on permissions
http://blogs.technet.com/b/speschka/archive/2009/10/28/using-the-developer-dashboard-in-sharepoint-2010.aspx

The on demand setting is really the optimal setting in my opinion.  Here’s what it gives you:  once it is set to on demand, site collection admins can turn it on or off.  When they do, it only turns it on or off for that particular site collection.  Equally as good, only the person that turned it on sees the output – your everyday users will not see the output from developer dashboard so this becomes a really valuable troubleshooting tool.  Even more interesting is that if you have multiple site collection admins and one of them toggles it on, the output is displayed only for that person, not for every site collection admin.   Want more flexibility?  Well you can even change the permissions that are required to see the dashboard output.  The DeveloperDashboardSettings has a property called RequiredPermissions.  You can assign a collection of base permissions (like EditLists, CreateGroups, ManageAlerts, or whatever you want) to it; only those people that have those permissions will be able to see the output.  So you have a great deal of flexibility and granularity in deciding when to use it the dashboard output and who will see it.