Administer > System configuration parameters > System performance parameters

System performance parameters

These parameters determine how the server manages system memory and fail over. You can set these parameters from the Service Manager server's operating system command prompt or from the Service Manager initialization file (sm.ini).

Startup parameter Description
Startup parameter: agstackl Defines the length of the stack the Service Manager server allocates to run RAD applications
Startup parameter: arraysizelimit Defines the maximum number of entries in an array.
Parameter: attachmentsegmentsize Determines the maximum number of bytes that each segment record in the SYSATTACHMENTS table can use
Startup parameter: cache_clean_interval Defines the interval that the Service Manager server waits before clearing the cache of infrequently used entries
Startup parameter: cache_locks Defines the number of locks that the Service Manager server allocates to the cache table
Startup parameter: cache_slots Defines the number of hash slots that the Service Manager server allocates to the cache table
Startup parameter: dao_sessiontimeout Specifies the number of seconds that the Service Manager server waits before terminating RESTful threads
Startup parameter: dao_threadsperprocess Specifies the maximum number of threads allowed to run concurrently in the process for a RESTful web service application
Special parameters: detectkeyed Causes the Service Manager server to display an alert message when a user attempts to run a nonkeyed query
Startup parameter: anubisPollInterval Specifies the time interval (in seconds) at which the anubis monitor checks to see if any registered scheduler is alive
Startup parameter: enableAnubisMonitor Starts the anubis monitor to check the status of background scheduler threads

Startup parameter: KMSearchEngineTimeout

Defines a timeout value in seconds for all Knowledge Management search server hosts
Startup parameter: maxgroupsperview Defines the maximum number of groups that can be used in a view
Startup parameter: maxhttpreqresponse Defines the maximum response size (in bytes) for HTTP requests
Startup parameter: maxKeepAliveRequests Allows you to override the Apache Tomcat server limit of processing 100 requests before ending a session
Startup parameter: maxloginspercluster Enables or disables Max Logins at the cluster level
Startup parameter: maxmemoryperthread Specifies the maximum memory (in MB) allowed for a session
Startup parameter: maxmsgsharedmemory Defines the maximum number of bytes of shared memory that the Service Manager server can use for unviewed messages
Startup parameter: maxpagesize Defines the maximum number of records that the Windows client requests from the server when displaying a record list
Startup parameter: memdebug Causes the Service Manager server to track or trace memory usage
Startup parameter: memmanager Specifies the memory manager to be used.
Startup parameter: precision Defines the number of decimal places at which the Service Manager server rounds numeric fields
Startup parameter: recordlistcount Sets the default number of records displayed in a record list.
Startup parameter: shared_memory Defines the amount of memory the Service Manager server sets aside for system caches and lock tables
Parameter: semaphoreWaitTime Defines the number of seconds the Service Manager server waits for a semaphore before generating a core dump
Startup parameter: shared_memory_address Ensures that the shared memory allocation is kept in an area that will not interfere with other applications on the server or the operating system
Startup parameter: shutipc Causes the Service Manager server to remove all IPC shared memory and semaphores
Parameter: strongtypecheck Specifies the strong type checking times for database records.
Startup parameter: tmpdirectory Defines the path where the Service Manager server can create and find temporary files for any file operation with Client Side Load/Unload and attachment handling
Startup parameter: usealtsignalstack Causes processes to handle StackOverFlow exceptions correctly
Startup parameter: usemembar Used by Service Manager to create a JVM
Parameter: vj_record_limit Sets the maximum number of records a virtual join may return on a subform
Parameter: vj_record_warning Specifies when the system writes a message to log file about virtual join record requests

Related topics

System parameters

Related topics

Enter a parameter in the sm.ini file