StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10547407
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-05-11T07:42:40.813
FavoriteCount
0
LastActivityDate
2014-11-18T11:34:28.463
LastEditDate
2014-11-18T11:34:28.463
LastEditorUserId
32824
OwnerUserId
32824
ParentId
591658
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Seeing that this is a popular question I've decided to explain what I did 3 years ago that sped up the ASP script. The original script made heavy use of resizable arrays in order to store key-values, so I modified that code to use Scriting.Dictionary. Example: <pre><code>Dim myDictionary Set myDictionary = Createobject("Scripting.Dictionary") myDictionary.item("key") = "value" </code></pre> That is a lot faster then resizable arrays. Another big change is the concatenation of strings. The original script was full of: <pre><code>S = "" S = S & "First line " S = S & "Second line " S = S & "Third line line " Response.Write(S) </code></pre> I modified this to: <pre><code>Response.Write("First line ") Response.Write("Second line ") Response.Write("Third line ") </code></pre> This made a huge difference. The concatenation of strings is a huge bottleneck because the string is thrown away and then reinitialized. Another option is: <pre><code>S = "First line " & _ "Second line " & _ "Third line line " Response.Write(S) </code></pre> This is also a good tip for ASP.NET: Use a StringBuilder instead of concatenating strings. Another important change is context switching. The original code was full of: <pre><code><table> <tr> <td><%= rs("Col1") %></td> <td><%= rs("Col2") %></td> <td><%= rs("Col2") %></td> </tr> </table> </code></pre> The 3 context switches take up a lot of time so I modified to this: <pre><code><% Response.Write("<table>") Response.Write("<tr>") Response.Write("<td>") Response.Write(rs("Col1")) Response.Write("</td>") Response.Write("</tr>") Response.Write("<tr>") Response.Write("<td>") Response.Write(rs("Col2")) Response.Write("</td>") Response.Write("</tr>") Response.Write("<tr>") Response.Write("<td>") Response.Write(rs("Col3")) Response.Write("</td>") Response.Write("</tr>") Response.Write("</table>") %> </code></pre> Yes the code is very redundant but it performs better. Another small modification (which is actually a dirty hack) is to use WITH (NOLOCK) in your SQL queries: <pre><code>conn.Query("SELECT * FROM MyTable WITH (NOLOCK) LEFT JOIN AnotherTable WITH (NOLOCK) ON MyTable.Id = AnotherTable.Id") </code></pre> It makes a difference. Finally, I don't know if that helps much, but there was a lot of copy-pasted code that I refactored into clean functions. I hope that people finding this thead will find these tips useful.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPerformance tips for classic asp?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmghaoui
UserOwnerUserId
1. USmghaoui
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. COMy comment got downvoted to 0? Really? Did the person who downvoted actually read the thread?
 singulars
 PostPostId
 PO
 UserUserId
 USmghaoui

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.