1. If you specify a DB when configure Controller, run information will store in the DB, you can query run information from the DB.
2. Also after you finish your result, there will be generate a *.trx file in your TestResults folder that under the same path with your web performance project, double click can get the summary information about this run(before that you need to add a web performance project,maybe it's a bug.:)), let's start to read some key point about the summary report.(Before read the result, make sure you has permisson to connect the DB that controller specify, if not, maybe you need to open VS with the user that has DB access permisson)
Overall:
http://msdn.microsoft.com/en-us/library/bb924371.aspx
Result fied meaning:
http://msdn.microsoft.com/en-us/library/ms404705.aspx
The key point:
End-user response times(will be the first should be focus)
Average response time is for all requests like default.aspx, but also think of your dependent requests (.js, .gif, .css, etc. etc.).
So the Page Time consists of the base page response + the retrieval of all the dependents.
Also you can set a time Response Time Goal for every request like below or defined in code.
http://msdn.microsoft.com/en-us/library/ms404691.aspx
request1.ResponseTimeGoal = 50;