Hi Firebird Developers!
I access Firebird frequently from Windows services running on the same machine.
I have a huge number of accesses each with small impact, many updates and
inserts rather than selects. Roundtrip time is very critical. I'm using the
Firebird ADO.NET driver, thus doing localhost/loopback TCP communication.
Compared to MS SQL, Firdbird's localhost TCP roundtrips from Client to Server
for doing things like single-row inserts or updates take significantly longer.
There may be a several reasons for this. One simple improvement would be to
switch the SIO_LOOPBACK_FAST_PATH socket option ON on the Windows platform.
A request has already been file here
http://tracker.firebirdsql.org/browse/CORE-4563 but it's tagged as minor
priority, so will probably not get addressed soon.
What I can say is that implementing this could cause a significant performance
gain at rather little effort. With other loopback TCP communications in my own
applications I realized a 20+ % improvement in transporting data packets.
I'd suggest to define a new firebird.config setting (default off), to reduce
the risk. I could provide code for the Firebird ADO.NET driver side and, if
someone could point me to the right direction, I would also prepare a change in
the Firebird C++ code to set this option. (However currently I don't have the
tools to compile Firebird.)
What I'd love to see is this feature in the next 2.5.x release (and in 3.0 as
well, of course, but currently we're still with 2.5).
Karsten
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
