StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14904669
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-15T22:48:30.747
FavoriteCount
0
LastActivityDate
2013-02-15T22:48:30.747
LastEditDate
LastEditorUserId
0
OwnerUserId
2075201
ParentId
14167394
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
Here is the code I am using for a movie database playground. I experimented with jQuery events, but finally decided that it is enough if the data is transferred continuously. My testing collection is 680 records, with 20 fields and one thumbnail field which is between 10-20kb per cover. Here the Coffeescript code: <pre><code>Movies = new Meteor.Collection("movies") if Meteor.isClient # starting with 10 items that the user sees a page fast Session.set("queryLimit", 10) # getting the item count from the server collection Meteor.call 'getMoviesCount', (err, result) => Session.set('itemsInQuery',result) # subscribe to a subset of the collection, and change the Session var on completion # automatically changing the limit of the publishing function with autorun Meteor.autorun -> Meteor.subscribe "MoviesList", Session.get("queryLimit"), onComplete = -> if Session.get("queryLimit") < Session.get('itemsInQuery') queryLimit = Session.get("queryLimit") + 30 #change iterator depending on result size Session.set("queryLimit", queryLimit ) # Client helper to add more items to handlebars template Template.app.helpers movies: -> Movies.find({}) if Meteor.isServer Meteor.publish "MoviesList", (limit) -> # show whole collections once limit is reached, by setting limit to 0 limit = 0 if limit > Movies.find().count() console.log new Date(), limit Movies.find({}, { limit: limit, fields: {title:1 } } ) #use fields to test different result sizes Meteor.methods getMoviesCount: (query) -> return Movies.find().count() </code></pre> And the html: <pre><code><body> {{> app}} </body> <template name="app"> {{#each movies}} {{title}} {{/each}} </template> </code></pre> I did some quick performance test and it turns out that for a few lines of text per record, the quickest way to send data to the client is a limit around 100. I tried it also with 10-20kb thumbnails which are embedded in the file. When using bigger assets Chrome became quite unresponsive when the limit was bigger than 30 records. Here a few stats done on localhost (run 3x each): <pre><code>limit seconds till last record rendered. 0 79s 010 121s 020 64s 030 45s 050 34s 100 16s 200 16s </code></pre> It's interesting to note that it took around 79 s when meteor server sends the whole page in one go (limit=0). I am not sure, how this can be possible, because a continious stream should be the fastest. So there is probably something funny with my stats. Any ideas? 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIdeal way of doing infinite scroll and real time updates in Meteor
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAndrej
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POIdeal way of doing infinite scroll and real time updates in Meteor
 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
 VTBountyClose
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.