Ideally we're looking at a periodic aggregation of stats. So rather than keeping a record for every page request we aggregate these into a summary of page requests per hour, or day, or week or even month.
And we run the aggregation process daily or whatever period is deemed appropriate.
The idea is to allow trend analysis over a longer period. The theory being there is no need to hold all the page requests individually if you are reviewing total page requests daily for a month or whatever.
I like the idea Geoff. Can you give specifics as to how you'd like it to be done?
- A rough idea at the table structure.
- Does the way the stats gets recorded change?
Another idea:
How about take the best of two worlds? Record the stats the way they do now, but truncate after a certain amount of time (say 31 days). But also aggregate the stats into an overall table (numbers that never get deleted) These table would never grow large because they are just adding up numbers (possibly just one row of data or something. Maybe an xml file, not sure).
This would allow people to keep what they have now (they can choose "not" to use the truncation feature, or choose how far back they want to truncate) which allows support for backwards compatability.
-Jeff C.
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
