on ‎2018 Jan 23 12:55 PM
Hi.
Is there any point in setting the cache limits on a server with 24 Gb, running a database on approx. 11 Gb? I'm thinking about the -c -cl and -ch parameters. And what is the point in setting "-ca 0" to disable automatic cache resize? Is there any situation where you want to use this parameter?
Regards,
Bjarne Anker
Request clarification before answering.
Here's an excerpt from this Foxhound 4 Help topic:
Performance Tip: If the computer is dedicated to running this SQL Anywhere server and no other process of importance, consider disabling the automatic cache size tuning process by specifying the -ca 0 and -c options to set a fixed cache size. With a dedicated computer there may be no need for SQL Anywhere to perform extra work changing the cache size up and down.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That being said, using the defaults may be helpful to get to know how much maximum cache size the database server will use for typical workloads... So I recommend to study the according properties and/or the according console log messages, and use the results to specify the -c option value...
| User | Count |
|---|---|
| 6 | |
| 5 | |
| 5 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.