StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6708742
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-15T14:39:55.960
FavoriteCount
0
LastActivityDate
2011-07-15T14:39:55.960
LastEditDate
LastEditorUserId
0
OwnerUserId
846463
ParentId
6704157
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Do you have a list of objects with set expiry times? e.g. obj1, expires at 12:35:01 obj2, expires at 12:37:14 obj3, expires at 12:38:56 obj4, expires at 12:43:44 If we know the expiry times when the collection is created we can use a single timer and a list of intervals to trigger the timer when the objects need to be removed e.g. <pre><code> Wait time in seconds To Be Removed int1 12:35:01 - now() obj1 int2 12:37:14 - 12:35:01 obj2 int3 12:38:56 - 12:37:14 obj3 int4 12:43:44 - 12:38:56 obj4 </code></pre> A) Peek the first entry in the 'delta list' (I have heard it called this before but could not give you a citation) and set the timer interval to the wait time. B) When the timer tiggers, remove the first entry from the delta list and do whatever needs to be done with the object from the source collection. Back to A When an item is added to the collection you need to add a new entry to the delta list in the correct position. Not overly complicated but allow for the timer popping while you are in the middle of adding. Pros: Only one timer. It's all you need. A timer per object is going to suck up a lot of resources. You only need to check through your whole collection at startup and then partial scans whenever new items are added. Never miss an expiry. It may not be important but a fixed time check means that we are late on removing some items. Cons: More complicated to implement than simply scanning the whole collection on a timer pop. Before changing anything, is the current implementation causing any problems? You will get a performance bump from the timer popping only when needed and from not having to scan the list each time. Are we talking 100 entries or 100,000? Would the performance bump be noticeable? You will no longer have any 'late' expiries (being removed from the list after their time out). Does this matter? hth, Alan
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I efficently use timers
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAlanT
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. This table or related slice is empty.
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.