jjjjL
11-07-2002, 07:54 PM
It just occured to me that it would be possible for me to store the stats for the current and next k value seperately. The stats for k=33661 could be on a seperate page and the current stats could remain online but would eventually settle down and stop being updated.
I don't know how people feel about this idea. I just thought of it so I haven't made up my mind yet. One benefit I can think of is that stats would be "speedier" because they could be in a new database. less data == faster.
Then again, the ramp up in the project lately sure does look neat. ;) I like the idea of leaving it all one group of stats too.
I recently optimized the database by indexing important columns so that stats now build about 100x faster and graphs take 10x less time to parse data. It's not imparitive that I choose either route, I'm just curious.
-Louie
I don't know how people feel about this idea. I just thought of it so I haven't made up my mind yet. One benefit I can think of is that stats would be "speedier" because they could be in a new database. less data == faster.
Then again, the ramp up in the project lately sure does look neat. ;) I like the idea of leaving it all one group of stats too.
I recently optimized the database by indexing important columns so that stats now build about 100x faster and graphs take 10x less time to parse data. It's not imparitive that I choose either route, I'm just curious.
-Louie