*better: More thorough, more relevant, more effective.
...more Alerts, more All Clears, more details, more control in your hands.
|
|
Foxhound is the better* Database Monitor for SQL Anywhere.
*better: More thorough, more relevant, more effective.
...more Alerts, more All Clears, more details, more control in your hands.
|
| [Home] | [Table of Contents] | [Previous Section] | [Next Section] |
Breck Carter
Last modified: February 12, 1998
mail to: bcarter@bcarter.com
There is no absolute limit to the number of connections SQL Anywhere can handle. However, the -gn or THREAD_COUNT option is limited to 100, meaning that with more than 100 concurrent users there may be delays because an execution thread is not available to service a database request. The practical maximum may be around 20 to 30 heavy users, or 40 to 50 users if they're not all making requests all the time.
With many client server applications each user spends most of the time working with data on the client and only submits database requests once in a while. For example, if the average user makes a database request every minute, and the server takes 1/10th of a minute (6 seconds) to satisfy that request, then one execution thread might be able to handle ten users. That means "20 to 30 heavy users" could become 200 to 300 average users.
The real answer depends on your situation. One determined user running the "Report From Hell" could bring the server to its knees whereas the load from a roomful of people doing data entry might not even be felt.
| [Home] | [Table of Contents] | [Previous Section] | [Next Section] |