>From an IT operations side it is so nice and easy to run top on linux and see all of the processes for classic. For superserver and superclassic that is all mostly hidden in threads for a single process and you can't terminate a single thread through the OS tools in the case of an emergency.
-steve On Sun, Jan 17, 2016 at 4:44 AM, Thomas Steinmaurer [email protected] [firebird-support] <[email protected]> wrote: > > > > On 17-1-2016 00:07, Köditz, Martin [email protected] > > [firebird-support] wrote: > >> is there still a reason to use the Classic mode with Firebird 3? Since > >> there is real SMP support with SuperServer I don’t think there can be > >> advantages with ClassicServer. > > > > The main advantage of course is that if one connection does something > > (hit a bug in the engine or in a UDF) that crashes the process, that it > > doesn't bring down all connections, but just that one connection. > > The number one reason why Classic hasn't been vanished yet, cause big > customers with critical environments are still opting for Classic. > > -- > With regards, > Thomas Steinmaurer > http://www.upscene.com/ > > Professional Tools and Services for Firebird > FB TraceManager, IB LogManager, Database Health Check, Tuning etc. > >
