StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
242166
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-10-28T03:33:42.687
FavoriteCount
0
LastActivityDate
2008-10-28T03:51:56.563
LastEditDate
2008-10-28T03:51:56.563
LastEditorUserId
29157
OwnerUserId
29157
ParentId
242160
PostTypeId
2
Score
20
ViewCount
0
LastEditorDisplayName
Adam Liss
text
Body
Logging tells you what happened. It's great for forensics and debugging. Profiling quantifies that: it tells you how much time your code spent in each area, or how many times a body of code was executed. It helps you improve your code's performance. Profiling typically operates at the level of a line of code, a function call, or sometimes a file. For each level, it can typically tell you: <ul> <li>How many times the unit was executed. It's generally less important to optimize rarely-used code than code that executes millions of times. One exception is code that makes a user (or another process) wait for it to complete.</li> <li>How many times a branch was taken, say in an <code>if</code> or <code>switch</code> statement. Again, you typically care most about optimizing often-used code.</li> <li>How much time was spent in a particular function. Warning: even experienced developers are often surprised by these results. It's very difficult to predict where your "time sinks" are.</li> <li>How much time was spent in a function and all functions called within that function. Maybe it's not the function itself, but its children, that need optimizing.</li> <li>How many times the unit was called by each caller. You may find that a particular function is called primarily from an unexpected place.</li> </ul> Armed with the data from a good profiler, you can often gain significant improvements in performance with relatively little effort.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow is profiling different from logging?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAdam Liss
UserOwnerUserId
1. USAdam Liss
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow is profiling different from logging?
 singulars
 PostTypePostTypeId
 PTQuestion
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. 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.