> 11.11.2016 10:06, Karsten Strobel wrote: > > 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. > > The most viable one that MS SQL uses shared memory for talking with local > server, not TCP. You could use it as well with Firebird 3.0 using xnet:// > prefix > to force XNET protocol. Though I don't know if .NET provider supports that.
There are plenty of use cases where xnet may not be the desired protocol. The new Windows API would actually improve performance for applications on the db host used TCP, where the IP address used in the connection was that of the host itself (ie. The improvement does not depend on the use of 127.0.0.1 as the IP address). > If you care about performance, perhaps you'd better to abandon .NET and > switch to native code. This type of comment has no place in discussion regarding bugs or feature requests. There are plenty examples of .Net code which out perform C/C++ code. Sean ------------------------------------------------------------------------------ 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
