From: | Matthew Foster <matthew(dot)foster(at)noaa(dot)gov> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Strategy for doing number-crunching |
Date: | 2012-01-04 16:36:16 |
Message-ID: | CAP1ZYZGAXpa-WciBK-is5RB=eJ=+jqStUz28=Fy1HXrN4LDMiA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
We have a database with approximately 130M rows, and we need to produce
statistics (e.g. mean, standard deviation, etc.) on the data. Right now,
we're generating these stats via a single SELECT, and it is extremely
slow...like it can take hours to return results. The queries are variable,
so there is no way I can think of to "pre-calculate" the stats.
Here is an example query...
SELECT count(mae) AS count, to_char(avg(mae), 'FM990.999') AS mae,
to_char(avg(sqrt(rms)), 'FM990.999') AS rms, to_char(avg(bias),
'FM990.999') AS bias,
to_char(max(mae), 'FM990.999') AS mae_max, to_char(min(mae), 'FM990.999')
AS mae_min,
to_char(max(bias), 'FM990.999') AS bias_max, to_char(min(bias),
'FM990.999') AS bias_min,
to_char(max(sqrt(rms)), 'FM990.999') AS rms_max, to_char(min(sqrt(rms)),
'FM990.999') AS rms_min,
to_char(stddev(sqrt(rms)), 'FM990.999') AS rms_stddev,
to_char(stddev(mae), 'FM990.999') AS mae_stddev,
to_char(stddev(bias), 'FM990.999') AS bias_stddev
FROM verify_data.verification_data
WHERE model_name='foo'
AND...several other conditions...
As one might imagine, this query pounds the CPU relentlessly for hours.
I'm thinking there must be a better approach for doing large amounts of
calculations on the data. Any pointers would be greatly appreciated!
Matt
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-01-04 16:48:32 | Re: Strategy for doing number-crunching |
Previous Message | Birchall, Austen | 2012-01-04 12:00:56 | Removal of WAL logs |