Subject Re: [firebird-support] Re: Nagle Algorithm
Author Carlos H. Cantu
Re: [firebird-support] Re: Nagle Algorithm FB 3.0 (beta) was running in amazon AWS on Windows Server 2012R2.

Nothing special about fb.conf, I just changed the specific parameters (Compression and tcpbuffersize) depending on what was being tested.

For selects returning thousands of records, the best speed was achieved with Compression turned ON, and TCPBuffer  set to 32K.

I have the slides of my talk and I can send to you, but they are in Portuguese.

Carlos H. Cantu
eBook Guia de Migração para o FB 3 - - -

Latestest stable version.  Something intesting about the benchmark article, what version an what OS, and a copy of the config..

Sent from Yahoo Mail for iPhone

On Wednesday, December 4, 2019, 6:12 AM, 'Carlos H. Cantu' listas@... [firebird-support] <> wrote:

You didn't say what version of Firebird you are using. If it is not
3.x, you can expect very bad performance transferring data over WAN.
FB 3 implemented changes in the wire protocol making things much
faster in high latency networks. The only remaining "problem" is if
you need to transfer blobs (it will be slow).

For more info:


nycfs> I was able to verify that NoNaggle appears to be marking the
nycfs> packets as push to avoid the Nagle Algorithm delays. The
nycfs> packets show up with push flag set from client and server.

nycfs> I am still very disappointed with the performance of the FB clients.

nycfs> An application that normally takes 25 seconds to open on LAN
nycfs> is taking 6 minutes to load on WAN.

nycfs> The actual data transferred is less than 11 Mbit.


nycfs> The bandwidth is not an issue, 100Mbps/100Mbps up/down.

nycfs> Point to Point Bandwidth tests show 95 Mbps with 7.6 ms round trip.


nycfs> Ping tests show client to server ping with 65500 bytes round trip time 19ms.

nycfs> Am I missing something here or what is slowing down these firebird communications???

nycfs> Any help would be appreciated.