The following properties are for performance issues. Please ensure that your settings will speed up the execution of i‑net Crystal-Clear and not slows them down.
The maximum queue length for incoming socket connection indications (i.e. connection requests). If a connection indication arrives when the queue is at its maximum length, the connection is refused. This property only has an effect for the Standalone Report Server.
Default value: 500
The Number of concurrent requests accepted before new requests are queued. This is also the number of concurrent running threads.
Recommended: 5 for a single processor machine (10 for 2 CPU machine, 20 for 4 CPU machine ...)
Default value: 5
The Number of concurrent HTTP requests accepted and handled by the Standalone Report Server. Further requests are queued.
Default value: 8
This property sets the maximum number of connections for one JDBC url.
If the maximum number of connections is exceeded and the login timeout is expired, a SQLException will be thrown.
A zero value means unlimited number of connections.
Note: MaxConnections must be >= n+1 where n is the maximum number of sub-reports of the report to be rendered, because each sub-report gets an own connection.
Default value: 5
The Connection Pool Timeout determines how long a connection will be held in the pool before being closed (in minutes). Accessing an open connection is much faster than creating a new one, so we suggest a time of at least 10 minutes. If you are really low on connections you may reduce this to 1 minute, but performance may degrade.
A value of 0 will disable the timeout completely, the connections will remain open forever.
Default value: 10
Login timeout for the JDBC drivers in seconds.
Default value: 30
Query timeout for a statement in seconds. The value 0 means there is no limit.
Default value: 300
The MetaData cache stores runtime information about database objects. Usually i-net Crystal-Clear will try to identify the database objects of a report when it is executed. That's why some JDBC meta data queries will be used. In fact if you request many reports with the same database objects or if you request a report many times then for each report meta data queries would be needed.
If you enable the MetaData cache the information about the database objects will be cached so that a second execution of a report would not need a JDBC meta data query anymore. Enabling the cache will enhance the speed of the report server.
Default value: false
If the MetaDataCache is used you can specify a timeout after which the information about a database object should be cleared from the cache. If you don't want to set a timeout you can set a value of zero. The timeout is specified in minutes.
Default value: 10
i‑net software strives to provide accurate product documentation. Please give us your feedback using the form below.
NOTE: This form is for documentation feedback only. For technical assistance, please send an email to crystalclear@inetsoftware.de.
