What about having two tables. One would be a kind of staging ground. You process all the records into it store them. It has a unique primary key instead of the timestamp. Then use that table to load up your summed by timestamp table, and clear out the temp table. When inserting records then you could load multiple records per insert statment (i think i settled on like 100 records per insert for a table I have with 20 colums, so you could probably manage many more than that.) Weather you realy need the extra table or not will depend on the quantity of records you are processing every 15 minutse.
Yet another optiuon would be to use the INSERT ON DUPLICATE KEY UPDATE syntax to have it sum them as it adds them. You could even right all those inserts into a text file then load the text file in mysql.
Good luck.
In reply to Re: DBI vs Bulk Loading
by eric256
in thread DBI vs Bulk Loading
by jimbus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |