>Due to the asymmetric communication, a bigger data output in a single
>packet (the result of using compression on the tunnel) will get sent
>without waiting. A smaller packet will delay a bit waiting for some
>additional data, which in your case does not come. You may want to
>check out this docum
> From: pgsql-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] On Behalf Of belal hamed
> Sent: 27 January 2013 13:16
> To: pgsql-performance@postgresql.org
> Subject: [PERFORM] PostgreSQL over internet
> by wireshark I monitor TCP packets I f
On Sun, Jan 27, 2013 at 03:09:55PM +0300, belal hamed wrote:
> >Here is your "problem". You need to understand the performance
> >characteristics of your communication channel. ADSL is a VERY
> >asymmetric communications channel. Down is usually much faster
> >than up.
>
> How it could be ADSL pro
>Here is your "problem". You need to understand the performance
>characteristics of your communication channel. ADSL is a VERY
>asymmetric communications channel. Down is usually much faster
>than up.
How it could be ADSL problem when it's the same in tow tests ?
beside data transferred when using
On 27/01/13 02:45, k...@rice.edu wrote:
On Sun, Jan 27, 2013 at 03:15:45AM +0300, belal hamed wrote:
I connect to my server through ADSL connection 4Mbps
Here is your "problem". You need to understand the performance
characteristics of your communication channel. ADSL is a VERY
asymmetric
On Sun, Jan 27, 2013 at 03:15:45AM +0300, belal hamed wrote:
>
> I connect to my server through ADSL connection 4Mbps
>
Here is your "problem". You need to understand the performance
characteristics of your communication channel. ADSL is a VERY
asymmetric communications channel. Down is usually
