StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHaving lots of open connections vs repeatedly opening and closing them
primarykey
Id
7994730
data
AcceptedAnswerId
7994770
AnswerCount
3
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-11-03T12:19:05.373
FavoriteCount
0
LastActivityDate
2011-11-03T12:25:57.960
LastEditDate
LastEditorUserId
0
OwnerUserId
7850
ParentId
0
PostTypeId
1
Score
1
ViewCount
225
LastEditorDisplayName
text
Body
<p>I'm investigating some performance issues in our product. We have several threads (order of tens) that are each doing some form of polling every couple of seconds, and every time we do that we are opening a connection to the DB, querying, then disposing.</p> <p>So I'm wondering, would it be more efficient for each thread to keep an open connection to the DB so we don't have to go through the overhead of opening a connection every 2 seconds? Or is it better to stick with the textbook <code>using</code> blocks?</p>
Tags
<c#><sql-server-2008>
Title
Having lots of open connections vs repeatedly opening and closing them
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USShaul Behr
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. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
3. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POHaving lots of open connections vs repeatedly opening and closing them
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COAre not DB connections themselves pooled ? What I mean is if you standard Oracle, Sql Server or MySQL, you get a feature of connection pooling. Rather than creating a new thread and disposing them, you could try to use thread from the thread pool, rather than creating each one every time
  singulars
  PostPostId
  POHaving lots of open connections vs repeatedly opening and closing them
  UserUserId
  USAnand

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.