MAXSAVE (JANUS DEFINE parameter): Difference between revisions
m (moved MAXSAVE to MAXSAVE (JANUS DEFINE parameter)) |
mNo edit summary |
||
| Line 2: | Line 2: | ||
<span class="pageSubtitle"><section begin="desc" />MAXSAVE xxx -- Max concurrent number of compiled SDS SQL requests.<section end="desc" /></span> | <span class="pageSubtitle"><section begin="desc" />MAXSAVE xxx -- Max concurrent number of compiled SDS SQL requests.<section end="desc" /></span> | ||
MAXSAVE is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]]. | <var>MAXSAVE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]]. | ||
This parameter specifies the maximum number of compiled SQL requests to save in CCATEMP. When the Specialty Data Store receives an SQL request from the Sybase Adaptive Server it parses the request, translates it into User Language, compiles the User Language into quads and finally evaluates the compiled User Language. When MAXSAVE is greater than 0, compiled requests are saved and future identical requests (except for constants) can simply load the compiled requests from CCATEMP (much like an APSY load), bypassing the translation and compilation steps. The default for MAXSAVE of 16 should be adequate for most situations, ensuring that frequently run requests will perform well without wasting CCATEMP and I/O bandwidth for infrequently run requests. | This parameter specifies the maximum number of compiled SQL requests to save in CCATEMP. When the Specialty Data Store receives an SQL request from the Sybase Adaptive Server it parses the request, translates it into User Language, compiles the User Language into quads and finally evaluates the compiled User Language. When <var>MAXSAVE</var> is greater than 0, compiled requests are saved and future identical requests (except for constants) can simply load the compiled requests from CCATEMP (much like an APSY load), bypassing the translation and compilation steps. | ||
The default for <var>MAXSAVE</var> of 16 should be adequate for most situations, ensuring that frequently run requests will perform well without wasting CCATEMP and I/O bandwidth for infrequently run requests. | |||
Valid only for SDS (also known as OMNI and OAS) ports. | Valid only for SDS (also known as OMNI and OAS) ports. | ||
Revision as of 19:04, 27 February 2012
<section begin="desc" />MAXSAVE xxx -- Max concurrent number of compiled SDS SQL requests.<section end="desc" />
MAXSAVE is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port. See the List of JANUS DEFINE parameters.
This parameter specifies the maximum number of compiled SQL requests to save in CCATEMP. When the Specialty Data Store receives an SQL request from the Sybase Adaptive Server it parses the request, translates it into User Language, compiles the User Language into quads and finally evaluates the compiled User Language. When MAXSAVE is greater than 0, compiled requests are saved and future identical requests (except for constants) can simply load the compiled requests from CCATEMP (much like an APSY load), bypassing the translation and compilation steps.
The default for MAXSAVE of 16 should be adequate for most situations, ensuring that frequently run requests will perform well without wasting CCATEMP and I/O bandwidth for infrequently run requests.
Valid only for SDS (also known as OMNI and OAS) ports.
References
See: List of Janus commands | List of JANUS DEFINE parameters.