StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11937832
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-13T15:50:12.923
FavoriteCount
0
LastActivityDate
2012-08-13T15:50:12.923
LastEditDate
LastEditorUserId
0
OwnerUserId
905
ParentId
11900134
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
Problem found, and it is with the routing tables (cheers Kirill). Basically we have lots of routes that look something like this: <pre><code>string[] controllers = GetListOfValidControllers(); routes.MapRoute( name: GetRouteName(), url: subfolder + "/{controller}/{action}/{id}", defaults: new { action = "Index", id = UrlParameter.Optional }, constraints: new { controller = "(" + string.Join("|", controllers) + ")" }); </code></pre> It turns out that <a href="http://samsaffron.com/archive/2011/10/13/optimising-asp-net-mvc3-routing">the Regex check is very slow</a>, painfully slow. So I replaced it with an implementation of <code>IRouteConstraint</code> that just checks against a <code>HashSet</code> instead. Then I changed the map route call: <pre><code>routes.MapRoute( name: GetRouteName(), url: subfolder + "/{controller}/{action}/{id}", defaults: new { action = "Index", id = UrlParameter.Optional }, constraints: new { controller = new HashSetConstraint(controllers) }); </code></pre> I also used the <a href="http://samsaffron.com/archive/2011/10/13/optimising-asp-net-mvc3-routing">RegexConstraint mentioned in that linked article</a> for anything more complicated - including lots of calls like this (because we have legacy WebForm pages): <pre><code>routes.IgnoreRoute( url: "{*allaspx}", constraints: new { allaspx = new RegexConstraint( @".*\.as[pmh]x(/.*)?") }); </code></pre> Those two simple changes completely fix the problem; <code>Url.Action</code> and <code>Html.BeginForm</code> now take a negligible amount of time (even with lots of routes).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFirst call to Url.Action on a page is slow
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USKeith
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFirst call to Url.Action on a page is slow
 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
 VTAcceptedByOriginator
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.