From: Mischa Sandberg <mischa.sandberg@telus.net>
To: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: Joel Fradkin <jfradkin@wazagua.com>
Cc: Andreas Pflug <pgadmin@pse-consulting.de>
Cc: Dave Page <dpage@vale-housing.co.uk>
Cc: pgsql-performance@postgresql.org, ac@wazagua.com, "Joshua D. Drake" <jd@commandprompt.com>
Cc: wheyliger@wazagua.com, 'Steve Hatt' <shatt@wazagua.com>
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
Date: Fri, 22 Apr 2005 13:53:50 -0700
Message-ID: <1114203230.4269645e44160@webmail.telus.net> (raw)
In-Reply-To: <20050422183054.GB14419@dcc.uchile.cl>
References: <4268C833.8080302@pse-consulting.de>
<000401c54763$dd684620$797ba8c0@jfradkin>
<20050422183054.GB14419@dcc.uchile.cl>
Quoting Alvaro Herrera <alvherre@dcc.uchile.cl>:
> One further question is: is this really a meaningful test? I mean, in
> production are you going to query 300000 rows regularly? And is the
> system always going to be used by only one user? I guess the question
> is if this big select is representative of the load you expect in
> production.
While there may be some far-out queries that nobody would try,
you might be surprised what becomes the norm for queries,
as soon as the engine feasibly supports them. SQL is used for
warehouse and olap apps, as a data queue, and as the co-ordinator
or bridge for (non-SQL) replication apps. In all of these,
you see large updates, large result sets and volatile tables
("large" to me means over 20% of a table and over 1M rows).
To answer your specific question: yes, every 30 mins,
in a data redistribution app that makes a 1M-row query,
and writes ~1000 individual update files, of overlapping sets of rows.
It's the kind of operation SQL doesn't do well,
so you have to rely on one big query to get the data out.
My 2c
--
"Dreams come true, not free." -- S.Sondheim, ITW
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mischa.sandberg@telus.net, alvherre@dcc.uchile.cl, jfradkin@wazagua.com, pgadmin@pse-consulting.de, dpage@vale-housing.co.uk, jd@commandprompt.com, shatt@wazagua.com
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
In-Reply-To: <1114203230.4269645e44160@webmail.telus.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox