StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4027976
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-10-26T20:59:14.343
FavoriteCount
0
LastActivityDate
2010-10-26T20:59:14.343
LastEditDate
LastEditorUserId
0
OwnerUserId
224279
ParentId
4026703
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Three observations. <ol> <li>The best speedups are not coming from optimizations but from good algorithms. So make sure you get that part right first. Often this means just using the right libraries for your specific domain. </li> <li>Once you get your algorithms right it is time to Measure. Often there is an 80/20 rule at work. 20% of your code will take 80% of the execution time. But in order to locate that part you need a good profiler. <a href="http://software.intel.com/en-us/articles/intel-vtune/" rel="nofollow">Intel VTune</a> can give you sampling profile from every function and nice reports that pinpoint the performance killers. Another free alternative is <a href="http://developer.amd.com/cpu/CodeAnalyst/Pages/default.aspx" rel="nofollow">AMD CodeAnalyst</a> if you have an AMD CPU.</li> <li>The compiler autovectorization capability is not a silver bullet. Although it will try really hard (especially <a href="http://software.intel.com/en-us/articles/intel-compilers/" rel="nofollow">Intel C++</a>) you will often need to help it by rewriting the algorithms in vector form. You can often get much better results by handcrafting small portions of the bottleneck code to use SIMD instructions. You can do that in C code (see VJo's link above) using intrinsics or use inline assembly. </li> </ol> Of course parts 2 and 3 form an iterative process. If you are really serious about this then there are some good books on the subject by Intel folks such as <a href="http://rads.stackoverflow.com/amzn/click/0976483211" rel="nofollow">The Software Optimization Cookbook</a> and the processor reference manuals.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POc++ how to write code the compiler can easily optimize for SIMD?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USrenick
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.