Several options can have a major impact on database server performance, including:
Cache size The -c option controls the amount of memory that SQL Anywhere uses as a cache. This can be a major factor in affecting performance.
Generally speaking, the more memory made available to the database server, the faster it performs. The cache holds information that may be required more than once. Accessing information in cache is many times faster than accessing it from disk. The default initial cache size is computed based on the amount of physical memory, the operating system, and the size of the database files. On Windows and Unix operating systems, the database server automatically grows the cache when the available cache is exhausted.
The Server Messages window displays the size of the cache at startup, and you can use the following statement to obtain the current size of the cache:
SELECT PROPERTY( 'CacheSize' )
For more information about performance tuning, see Monitoring and Improving Performance.
For more information about controlling cache size, see -c server option.
Multiprogramming level The database server's multiprogramming level is the maximum number of server tasks that can execute concurrently. In general, a higher multiprogramming level increases the overall throughput of the server by permitting more requests to execute simultaneously. However, if the requests compete for the same resources, increasing the multiprogramming level can lead to additional contention and actually increase transaction response time, or in some cases even lower the system's throughput. You can set the server's multiprogramming level with the -gn option. See -gn server option and Setting the database server's multiprogramming level.
Number of processors If you are running on a multi-processor computer using a network database server, you can set the number of processors with the -gt option. See -gt server option and Threading in SQL Anywhere.
Other performance-related options There are several options available for tuning network performance, including -gb (database process priority), and -u (buffered disk I/O).