You are probably right. Another important variable is the radius of the marker: you can dramatically change the bloatedness of your map and data requirements by simply changing the size of your marker.
This option I would like to use a bit later once I understand what the client limitations are.
why don’t you do the calculation in the server before publishing them ?
I have done an in-house project where when I do the calculation in the client it will be unresponsive like forever too…
But as usual, people use that data in template helpers to render in #each and than even dont subscribe correctly.
totally true… so I am using msaving:mongoland/or babrahams:constellation to see the subscribe data
I think that is the way. I am looking at meteorhacks:aggregate. Working on modifying the code. 