I'd start with a simple implementation with no pre-calculation and test to see how inefficient it is. Get some ballpark numbers for the number of potential users and events-per-user, load up some test data, and give it a try. If it's fast enough, you're done. Don't look back.
If it's not, then yes, pre-calculate. But be sure to treat it as cache data - ready to be invalidated if anything about an event changes. Finding all the invalidation points may be challenging if you don't have good data-encapsulation. All the more reason to invest now in a clean database abstraction that will give you a good way to add caching like this. If you do your job right none of the client code should change when your events switch from calculated on the fly to pre-calculated.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||