StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
227454
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-10-22T20:37:31.957
FavoriteCount
0
LastActivityDate
2008-10-29T18:49:13.210
LastEditDate
2008-10-29T18:49:13.210
LastEditorUserId
30454
OwnerUserId
30454
ParentId
227148
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
trebormf
text
Body
Normally, if you see a non-linear increase in processing time vs. input size, you should suspect your code more than the framework. But since the problem goes away when the tool is compiled with .NET 2.0, all bets are off. With XSLT, it's hard to create a non-linear performance curve if you do all your parsing with straight template matches: <pre><code><xsl:template match="foo">  <xsl:apply-templates / >  </xsl:template> <xsl:template match="bar">  <xsl:apply-templates / >  </xsl:template> </code></pre> Pay careful attention to anywhere you might have resorted to <code><xsl:for-each></code> for parsing; template matches are virtually always a better way to achieve the same result. One way to troubleshoot this performance problem is to recreate your XSLT one template-match at a time, testing the processing time after adding each match. You might start with this match: <pre><code><xsl:template match="*"> <xsl:copy>  <xsl:copy-of select="@*"/>  <xsl:apply-templates />  </xsl:copy> </xsl:template> </code></pre> This will match and copy every node, one at a time, to a new document. This should not exhibit a non-linear increase in processing time vs. input size (if it does, then the problem is not with your XSLT code). As you recreate your XSLT, if you add a template-match that suddenly kills performance, comment out every block inside the template. Then, uncomment one block at a time, testing the processing time each iteration, until you find the block that causes the problem.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT Transform Efficiency
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UStrebormf
UserOwnerUserId
1. UStrebormf
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.