From: Peter M. <P.m...@de...> - 2004-02-27 07:45:15
|
No, from what I have seen, C# is slightly slower than a well written C++ program doing the same thing. But if you start counting your own time to it to make it robust, than my choice is clear. And if you can use multiple threads, .net is definitively a better choice. I have not benchmarked the C API of Firebird. Peter _____ Van: fir...@li... [mailto:fir...@li...] Namens Da Jiao Verzonden: donderdag 26 februari 2004 21:51 Aan: 'FB-NETProvider' Onderwerp: Re: [Firebird-net-provider] .NET provider Performance Thank you, Peter, I am concerning the speed to access Firebird, I am working on the server side and not worrying UI performance. Are you saying C# net provider is faster than C++ API to run the same query against Firebird? ----- Original Message ----- From: Peter Martens <mailto:P.m...@de...> To: 'FB-NETProvider' <mailto:fir...@li...> Sent: Thursday, February 26, 2004 12:13 PM Subject: RE: [Firebird-net-provider] .NET provider Performance I do a lot of real-time work and C#.net is a lot faster for me than C++ because the multithreading is actually usable. Raw processing power is not a big difference. So if you are planning e.g. to use one thread for data-retrieval and another for GUI, .net is the only route... Peter _____ Van: fir...@li... <mailto:fir...@li...> [mailto:fir...@li...] Namens Da Jiao Verzonden: donderdag 26 februari 2004 20:59 Aan: FB-NETProvider Onderwerp: [Firebird-net-provider] .NET provider Performance Hello all, I am a newbie to Firebird, I am very glad that it has a .NET data provider. But I need to know more about its performance. Could anybody with practical experience with Firebird and its .NET provider tell me more info about its performance? I know using C++ API is the quickest way to access Firebird, if I use net-provider, what will be the performance penalty? If it is close enough, I will go the C# way. Any help is appreciated. Da Jiao |