In response to brauagustin-susc@yahoo.com.ar:
> >> > That's not what it looks like based on the EXPLAIN ANALYZE output.
> >> > It looks like run time dropped from two seconds to half a second.
> >>
> >> > It seems as though you either have a network delay delivering the results,
> >> > or your application is slow to read them.
> >>
> >> > Exactly how are you arriving at those timings you're reporting to us?
> >>
> >> I have noticed this in a daly process I run which involves normally 45 minutes and with the new server takes 1:40.
> >>
> >> Some days ago I began to do some tests with no success, then I opened PgAdmin with this simply query to read 2 big
tablesand then compare disk access.
> >> SELECT *
> >> FROM fact_ven_renta fvr, dim_producto_std_producto dpp
> >> WHERE
> >> fvr.producto_std_producto_sk = dpp.producto_sk
> >>
> >> fact_ven_renta has 136316 rows
> >> dim_producto_std_producto has 3669 rows
>
> >Run the tests from psql on the same server. As Kevin pointed out, the _server_ is faster, but it appears as if the
connectionbetween PGadmin and this new server is slower somehow.
>
> It runs quickly!!! But I don't know how to compare because looks like it retrieve fields by demand, when I put
ctrl+end(go to the last record) it use a lot of CPU and disk, run quickly anyway.
That's pretty odd. If you use \timing in psql, you can get execution
time for each query, if it helps you track things down.
> Correct me if am I wrong but, executing PgAdmin in the same server there aren't networks delays!
Not network, no. But the results of your explains seem to show that the
query is executing much faster on the new system than the old, so the
problem still becomes, "what is happening after the query completes that
is so slow?" It's just that networking is ruled out.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
wmoran@collaborativefusion.com
Phone: 412-422-3463x4023