Long running query hogs the server, why?

Short answer:

You need to use Firebird Classic.


Firebird comes in two different architectures, Classic and SuperServer. Super runs one thread per connection, while Classic runs one process per connection. This makes Classic somewhat heavier on resources, but it enables multiple users to run long-running queries and still not create a bottleneck for short transactions.

Since Firebird doesn't have good thread concurency in Super Server, you can use Classic and let your operating system and Firebird lock manager handle things.

Note: Classic was only supported on Linux before, but now there is support for Windows as well.

Alternatively, you can add a second server to do long running reports (OLAP) and keep Super Server for fast transactions (OLTP).

Do you find this FAQ incorrect or incomplete? Please e-mail us what needs to be changed. To ensure quality, each change is checked by our editors (and often tested on live Firebird databases), before it enters the main FAQ database. If you desire so, the changes will be credited to your name. To learn more, visit our add content page.

All contents are copyright © 2007-2024 FirebirdFAQ.org unless otherwise stated in the text.

Links   Firebird   News   FlameRobin   Powered by FB: Home Inventory   Euchre  
Add content   About  

 Installation and setup
 Backup and restore
 Connectivity and API
 Errors and error codes