Dimitry Sibiryakov wrote: > 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. > If you care about performance, perhaps you'd better to abandon .NET and > switch to > native code.
Abandoning .NET if surely no option for me. Our entire product is based on .NET and uses Entity Framework. Changing this is impossible (and undesired). Unfortunately the Firebird ADO.NET driver doesn't support the xnet protocol to a local FB server. Enabling the Loopback Fast Path option is a few lines of code only (both on client and server side), compared to implementing xnet in ADO.NET that's very little effort. 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
