MySQL Forums
Forum List  »  Performance

Averaging data on the fly vs Second Table
Posted by: Peter Brown
Date: April 03, 2009 07:30PM

I'm working on a project where I will be logging weather data at one second intervals; each second will represent one record in the database table once inserted.

I will be graphing this data on daily, weekly, monthly and yearly intervals. For the larger date ranges, I would like to convert to quarter-hourly, hourly, an/or daily averages so that graph rendering is much faster.

My first question is whether MySQL is capable of handling the averaging calculations on the fly or does it makes more sense to create separate database tables that have this data pre-calculated?

My second question is after a year there will be 30+ million records. Will performance be greatly affected with this much data?

Options: ReplyQuote

Written By
Averaging data on the fly vs Second Table
April 03, 2009 07:30PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.