Original post by DEbig3
As opposed to a user not logging in for a week, and then having to calculate 10k updates?
I doubt this is a problem. 10k is not very much, that's just about 1 ‰ of the number of rays a very basic realtime ray tracer can trace each second. Of course a web-server is usually not fast, as are most languages when compared to non-beginner C++.
So let's assume a tick is needed once per second:
= 60 ticks/minute
= 3.600 ticks/hour
= 86.400 ticks/day
= 604.800 ticks/week
= 2.419.200 ticks/(28 days)
Advice A) Benchmark how long it takes for so many ticks. If it is just 10 seconds or less, I'd say we have no problem (in case this technique is applicable)
Advice B) Do you really need 1 tick/second? In case 1 tick/(30 seconds) would be enough, e.g., you would only have 80640 ticks/(28 days). Then go back to A).
(again, this is only in case the technique is applicable and to show actual numbers)