From: | "NSO" <nso(at)fmf(dot)vtu(dot)lt> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Bytea poor performance |
Date: | 2005-10-15 16:16:30 |
Message-ID: | 18133.81.7.89.65.1129392990.squirrel@fmf.vtu.lt |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hello,
Yes, I can understand that, but then why the same app on the server
machine is done in 4 seconds? (big difference from 20-30 seconds). I
tryed to monitor network traffic and it is used only for 1-2% of total
100mbit.
> "NSO" <nso(at)fmf(dot)vtu(dot)lt> writes:
>> Query runs very long:
>> Total query runtime: 23625 ms.
>> Data retrieval runtime: 266 ms.
>> 50 rows retrieved.
>
> Notice that the query itself took 266ms. The rest of the time was
> wasted by your client app trying to format a 23Kb by 50 row table
> for display. You need to replace your client-side code with something
> less inefficient about handling wide values.
>
> regards, tom lane
>
> --
> This message has been scanned for viruses and
> dangerous content, and is believed to be clean.
>
>
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-10-15 16:24:24 | Re: Bytea poor performance |
Previous Message | Tom Lane | 2005-10-15 15:54:07 | Re: Bytea poor performance |