MAXSAVE (JANUS DEFINE parameter): Difference between revisions
mNo edit summary |
m (remove displaytitle) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle">MAXSAVE xxx — Max concurrent number of compiled SDS SQL requests</span> | |||
<span class="pageSubtitle" | |||
<var>MAXSAVE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port | <var>MAXSAVE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
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. | This parameter specifies the maximum number of compiled SQL requests to save in CCATEMP. When the <var class="product">[[Media:JsdsrNew.pdf|Specialty Data Store]]</var> receives an SQL request from the <var class="product">Sybase Adaptive Server</var> it parses the request, translates it into <var class="product">User Language</var>, compiles the <var class="product">User Language</var> into quads and finally evaluates the compiled <var class="product">User Language</var>. 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. | 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 <var>[[JANUS DEFINE#type|SDS]]</var> (also known as <var>[[JANUS DEFINE#type|OMNI]]</var> and <var>[[JANUS DEFINE#type|OAS]]</var>) ports. | ||
== | ==See also== | ||
<ul> | |||
<li>[[List of Janus commands]] | |||
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] | |||
</ul> | |||
[[Category:JANUS DEFINE parameters|MAXSAVE]] | [[Category:JANUS DEFINE parameters|MAXSAVE]] | ||
Latest revision as of 00:22, 8 June 2016
MAXSAVE xxx — Max concurrent number of compiled SDS SQL requests
MAXSAVE is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
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.