From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Clemens Eisserer <linuxhippy(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Slow query execution over WAN network |
Date: | 2011-02-24 17:43:29 |
Message-ID: | AANLkTikyiMEnemQPmQvVyV_bQ93gzTJu2sZRNk4GJaVt@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Thu, Feb 24, 2011 at 9:56 AM, Clemens Eisserer <linuxhippy(at)gmail(dot)com> wrote:
> Hi,
>
> I experience really slow query execution over remote networks,
> especially for a query which returns a lot of columns (~255) caused by
> joins.
>
> Executing the same query over different networks gives the following times:
> Local: 20ms
> DSL: 400ms
> UMTS: 1500ms
>
> The query returns 12 rows, and 255 column - most of them with only
> very little data. A wireshark-snapshot of a request is only ~30kb
> large, so I guess there isn't a lot of data transported.
>
> I've uploaded a netbeans-profiler screenshot as well as a wireshark profile to:
> http://93.190.88.182/jdbc_traffic.wireshark
> http://93.190.88.182/jdbc_profile.png
>
> Any idea whats causing the high latency? Are there multiple
> round-trips going on here?
> I already tried adjusting fetch size, however didn't change anything.
>
> Thank you in advance, Clemens
>
> PS: I've asked the question already on pgsql-performance,
> unfourtunatly there wasn't a lot of feedback. Sorry for cross-posting.
The problem is the data coming back I'm sure the WAN is slower than your DSL.
Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Maciek Sakrejda | 2011-02-24 18:38:25 | Re: difference on execution time between prepared statement in pgAdmin and through JDBC Stack |
Previous Message | Radosław Smogura | 2011-02-24 17:07:51 | Re: Slow query execution over WAN network |