StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13137528
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-30T10:58:37.397
FavoriteCount
0
LastActivityDate
2012-10-30T11:05:10.530
LastEditDate
2012-10-30T11:05:10.530
LastEditorUserId
2753
OwnerUserId
2753
ParentId
13137211
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Make sure that you really know what you're looking for in the profiler you're writing, whenever you're collecting the total execution time of a certain piece of code, it will include time spent in all its children and it may be hard to really find what is the bottleneck in your system as the most top-level function will always bubble up as the most expensive one - like for instance main(). What I would suggest is to hook into every function's prologue and epilogue (if your application is a CLR application, you can use the <a href="http://msdn.microsoft.com/en-us/library/ms231434.aspx" rel="nofollow"><code>ICorProfilerInfo::SetEnterLeaveFunctionHooks</code></a> to do that, you can also use macros at the beginning of every method, or any other mechanism that would inject your code at the beginning and and of every function) and collect your times in a form of a tree for each thread that your profiling. The algorithm for this would look somehow similar to this: <ul> <li>For each thread that you're monitoring create a stack-like data structure.</li> <li>Whenever you're notified about a function that began execution, push something that would identify the function into that stack. <ul> <li>If that function is not the only function on the stack, then you know that the previous function that did not return yet was the one that called your function.</li> <li>Keep track of those callee-called relationships in your favorite data structure.</li> </ul></li> <li>Whenever a method returns, it's identifier will always be on top of its thread stack. It's total execution time is equal to (time when the last (it's) identifier was pushed on the stack - current time). Pop that identifier of the stack.</li> </ul> This way you'll have a tree-like breakdown of what eats up your execution time where you can see what child calls account for the total execution time of a function. Have fun!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POProfiling algorithm
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USKarim Agha
UserOwnerUserId
1. USKarim Agha
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.