This program was written with the only purpose: to check the users claims about frequent lost of Firebird database connections that were not confirmed by other simple methods, such as ping.
The program algorithm is very simple: it connects to database and do the set of SQL queries in defined period of time. The total execution time of SQL sets is registered in protocol.
If database connection was lost - this is also registered in protocol and program tries to restore connect to database. After connection was restored, the testing continues.
By changing SQL query and amount of queries in the set, one could change the testing accent: shift it to the server response (some hard queries) or to network capacity (a lot of short queries).
Daytime monitoring could highlight moments of peak load on server or network.
Running monitoring simultaneously on several client computers could localize the bottlenecks in the system: do clear whether slow work is caused by server problems or by network.
(total votes: 0)
This program was written with the only purpose: to check the users claims about frequent lost of Firebird database connections that were not confirmed by other simple methods, such as ping.
