In general, the defaults for ADS are chosen to be optimal for most users. To tweak settings to your specific needs, look at General Performance Factors.
Other suggestions:
Bitness: Use the 64-bit ADS server.
Cache: Adjust the registry setting MAX_CACHE_MEMORY. By default, ADS uses roughly 50% of available physical RAM for the cache (or 256MB for the 32-bit server). If your application is not running on the same machine, and no other processes are competing for memory, you can increase this value.
Startup parameters: See: Viewing Configuration Parameters Affecting Memory. Most editable values are dynamic, meaning more resources will be allocated as needed. However, if processing is slow after restarting the server, increasing these values may save the time it takes for these values to climb to the appropriate level.
Protocols: If an application is on the same host as the ADS server, IPC (shared memory) will be used. This is the fastest protocol. If the application is on another machine, or if IPC is disabled, UDP can be much faster than TCP. However, if there is contention or noise on the network, UDP can bog down because it needs to resend requests and wait for replies. In this case TCP will be faster.
Flush frequency: If slowdowns are experienced after about 10 minutes of heavy activity, the Flush Frequency may need to be adjusted either up or down. Higher values may help if the heavy activity usually subsides after a few minutes. Lower values may dilute the performance impact.
As with any database server, there are countless scenarios where poor performance may require a specialized tweak. You can search our Knowledge Base from the Launchpad or post more specific issues here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.