Feedback
Did this article resolve your question/issue?

   

Article

RAM consumption when disk caching is disabled using Openaccess SDK.

Information

 
TitleRAM consumption when disk caching is disabled using Openaccess SDK.
URL NameIf-the-caching-is-disabled-should-we-expect-the-increased-consumption-of-RAM
Article Number000181279
EnvironmentProduct: Openaccess SDK
Version: 7.2
OS: Linux
Database: Openaccess
Application: All supported applications
Question/Problem Description
When disk caching is disabled, will there be an increased consumption of RAM?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
If the IP returns results in cursor mode, the consumption of RAM will be based on the size of DAM_INFO_FETCH_BLOCK_SIZE and the number of fields and size of the data in the query result.

In cursor mode, IP builds FETCH_BLOCK_SIZE rows of results and returns control to SQL Engine. These results are returned to the client application before the next set of results are requested. The DAM_INFO_FETCH_BLOCK_SIZE can be configured using ServiceSQLFetchBlockSize option.
Workaround
Notes
Last Modified Date4/29/2016 9:59 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.