GTBLHASH parameter - Revision history

DCameron: /* Calculating GTBL space requirements */

2014-10-28T12:19:44Z

Calculating GTBL space requirements

← Older revision		Revision as of 12:19, 28 October 2014
Line 42:		Line 42:
	<li>If both of these values are high, increase the size of GTBL by increasing LGTBL. </li>		<li>If both of these values are high, increase the size of GTBL by increasing LGTBL. </li>

	<li>If GTBLRU is high but GTBLRS is not, increase GTBLPCT or decrease GTBLHASH. </li>		<li>If GTBLRU is high but GTBLRS is not, increase <var>[[GTBLPCT_parameter\|GTBLPCT]]</var> or decrease GTBLHASH. </li>

	<li>If GTBLRS is high but GTBLRU is low, decrease GTBLPCT.</li>		<li>If GTBLRS is high but GTBLRU is low, decrease GTBLPCT.</li>

DCameron: /* Calculating GTBL space requirements */

2014-10-28T12:15:54Z

Calculating GTBL space requirements

← Older revision		Revision as of 12:15, 28 October 2014
Line 22:		Line 22:
	====Calculating GTBL space requirements====		====Calculating GTBL space requirements====
	<p>When hashed GTBL is being used, GTBL requires an extra 8 bytes for every hash bucket, which means that you should probably increase <var>[[LGTBL_parameter\|LGTBL]]</var> by at least 8 times the value of GTBLHASH. Since hashing does not distribute hash values exactly evenly between buckets, you should probably increase the size of GTBL by somewhat more than this for a little extra space in each bucket. </p>		<p>When hashed GTBL is being used, GTBL requires an extra 8 bytes for every hash bucket, which means that you should probably increase <var>[[LGTBL_parameter\|LGTBL]]</var> by at least 8 times the value of GTBLHASH. Since hashing does not distribute hash values exactly evenly between buckets, you should probably increase the size of GTBL by somewhat more than this for a little extra space in each bucket. </p>
	<p>~~Rocket Software recommends~~ that you increase LGTBL by GTBLHASH * (8 + <i>av_len</i> * 3) where <i>av_len</i> is the average expected length of the global string variable names, plus their values. So, if GTBLHASH is being set to seven and the average expected length of globals and their values is 20, LGTBL would be increased as follows: </p>		<p>It is recommended that you increase LGTBL by GTBLHASH * (8 + <i>av_len</i> * 3) where <i>av_len</i> is the average expected length of the global string variable names, plus their values. So, if GTBLHASH is being set to seven and the average expected length of globals and their values is 20, LGTBL would be increased as follows: </p>
	<p class="code">7 * (8 + 20 * 3) = 476.		<p class="code">7 * (8 + 20 * 3) = 476.
	</p>		</p>

DCameron: /* Calculating GTBL space requirements */

2014-10-28T12:15:05Z

Calculating GTBL space requirements

← Older revision		Revision as of 12:15, 28 October 2014
Line 21:		Line 21:
	<p>Resetting the GTBLHASH parameter clears the global table.</p>		<p>Resetting the GTBLHASH parameter clears the global table.</p>
	====Calculating GTBL space requirements====		====Calculating GTBL space requirements====
	<p>When hashed GTBL is being used, GTBL requires an extra 8 bytes for every hash bucket, which means that you should probably increase LGTBL by at least 8 times the value of GTBLHASH. Since hashing does not distribute hash values exactly evenly between buckets, you should probably increase the size of GTBL by somewhat more than this for a little extra space in each bucket. </p>		<p>When hashed GTBL is being used, GTBL requires an extra 8 bytes for every hash bucket, which means that you should probably increase <var>[[LGTBL_parameter\|LGTBL]]</var> by at least 8 times the value of GTBLHASH. Since hashing does not distribute hash values exactly evenly between buckets, you should probably increase the size of GTBL by somewhat more than this for a little extra space in each bucket. </p>
	<p>Rocket Software recommends that you increase LGTBL by GTBLHASH * (8 + <i>av_len</i> * 3) where <i>av_len</i> is the average expected length of the global string variable names, plus their values. So, if GTBLHASH is being set to seven and the average expected length of globals and their values is 20, LGTBL would be increased as follows: </p>		<p>Rocket Software recommends that you increase LGTBL by GTBLHASH * (8 + <i>av_len</i> * 3) where <i>av_len</i> is the average expected length of the global string variable names, plus their values. So, if GTBLHASH is being set to seven and the average expected length of globals and their values is 20, LGTBL would be increased as follows: </p>
	<p class="code">7 * (8 + 20 * 3) = 476.		<p class="code">7 * (8 + 20 * 3) = 476.

DCameron: /* Description */

2014-10-28T12:13:43Z

Description

← Older revision		Revision as of 12:13, 28 October 2014
Line 18:		Line 18:
	<p>When a global string variable is set or retrieved, the name of the global is hashed into one of the GTBLHASH buckets. Once the bucket is determined, the scanning and updating works as it did prior to Version 5.1, except there is less data to move when a value is deleted or its size changes.</p>		<p>When a global string variable is set or retrieved, the name of the global is hashed into one of the GTBLHASH buckets. Once the bucket is determined, the scanning and updating works as it did prior to Version 5.1, except there is less data to move when a value is deleted or its size changes.</p>
	<p>By default, when you place a global string variable in GTBL, it is stored in order-of-entry sequence. If you set GTBLHASH to a nonzero value the data is placed in GTBL in the order determined by the hash value of the global string variable name.</p>		<p>By default, when you place a global string variable in GTBL, it is stored in order-of-entry sequence. If you set GTBLHASH to a nonzero value the data is placed in GTBL in the order determined by the hash value of the global string variable name.</p>
	<p>~~Rocket Software recommends~~ that you set the number of buckets to a prime number, which is not greater than the expected maximum number of global variables divided by four. You can find your optimal value through experimentation~~; Rocket Software recommends~~ that you start with a relatively small number such as five or seven.</p>		<p>It is recommended that you set the number of buckets to a prime number, which is not greater than the expected maximum number of global variables divided by four. You can find your optimal value through experimentation, and that you start with a relatively small number such as five or seven.</p>
	<p>Resetting the GTBLHASH parameter clears the global table.</p>		<p>Resetting the GTBLHASH parameter clears the global table.</p>
	====Calculating GTBL space requirements====		====Calculating GTBL space requirements====

DCameron: /* Description */

2014-10-28T12:11:58Z

Description

← Older revision		Revision as of 12:11, 28 October 2014
Line 17:		Line 17:
	<p>The number of hash buckets allocated in GTBL to hold global string variable names. The benefit of using GTBLHASH is that the scan time and CPU time to find and update global string variables is reduced, typically, by a factor of GTBLHASH.</p>		<p>The number of hash buckets allocated in GTBL to hold global string variable names. The benefit of using GTBLHASH is that the scan time and CPU time to find and update global string variables is reduced, typically, by a factor of GTBLHASH.</p>
	<p>When a global string variable is set or retrieved, the name of the global is hashed into one of the GTBLHASH buckets. Once the bucket is determined, the scanning and updating works as it did prior to Version 5.1, except there is less data to move when a value is deleted or its size changes.</p>		<p>When a global string variable is set or retrieved, the name of the global is hashed into one of the GTBLHASH buckets. Once the bucket is determined, the scanning and updating works as it did prior to Version 5.1, except there is less data to move when a value is deleted or its size changes.</p>
	<p>By default, when you place a global string variable in GTBL, it is stored in order-of-entry. If you set GTBLHASH to a nonzero value the data is placed in GTBL in the order determined by the hash value of the global string variable name.</p>		<p>By default, when you place a global string variable in GTBL, it is stored in order-of-entry sequence. If you set GTBLHASH to a nonzero value the data is placed in GTBL in the order determined by the hash value of the global string variable name.</p>
	<p>Rocket Software recommends that you set the number of buckets to a prime number, which is not greater than the expected maximum number of global variables divided by four. You can find your optimal value through experimentation; Rocket Software recommends that you start with a relatively small number such as five or seven.</p>		<p>Rocket Software recommends that you set the number of buckets to a prime number, which is not greater than the expected maximum number of global variables divided by four. You can find your optimal value through experimentation; Rocket Software recommends that you start with a relatively small number such as five or seven.</p>
	<p>Resetting the GTBLHASH parameter clears the global table.</p>		<p>Resetting the GTBLHASH parameter clears the global table.</p>

DCameron: /* Summary */

2014-10-28T12:09:50Z

Summary

← Older revision		Revision as of 12:09, 28 October 2014
Line 11:		Line 11:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V6.1</var> ~~or earlier~~		<dd><var class="product">Model 204 V5.1</var>
	</dl>		</dl>

	==Description==		==Description==
	<p>The number of hash buckets allocated in GTBL to hold global string variable names. The benefit of using GTBLHASH is that the scan time and CPU time to find and update global string variables is reduced, typically, by a factor of GTBLHASH.</p>		<p>The number of hash buckets allocated in GTBL to hold global string variable names. The benefit of using GTBLHASH is that the scan time and CPU time to find and update global string variables is reduced, typically, by a factor of GTBLHASH.</p>

JAL at 20:56, 15 April 2014

2014-04-15T20:56:41Z

← Older revision		Revision as of 20:56, 15 April 2014
Line 29:		Line 29:

	<table>		<table>
	<tr><th>Statistic </th><th>Tracking</th></tr>		<tr class="head"><th>Statistic </th><th>Tracking</th></tr>

	<tr><th><var>GTBLRU </var></th><td>Number of GTBL rearrangements required to add a string variable global.</td></tr>		<tr><th><var>GTBLRU </var></th><td>Number of GTBL rearrangements required to add a string variable global.</td></tr>

	<tr><th><var>GTBLRS </var></th><td>Number of GTBL rearrangements required to add a global object. </td></tr>		<tr><th><var>GTBLRS </var></th><td>Number of GTBL rearrangements required to add a global object. </td></tr>
	</table>		</table>
	<p>After reviewing the GTBLRU and GTBLRS statistics, you can consider taking the following actions: </p>
			<p>
			After reviewing the GTBLRU and GTBLRS statistics, you can consider taking the following actions: </p>
	<ul>		<ul>
	<li>		<li>If both of these values are high, increase the size of GTBL by increasing LGTBL. </li>
	If both of these values are high, increase the size of GTBL by increasing LGTBL. </li>
	<li>		<li>If GTBLRU is high but GTBLRS is not, increase GTBLPCT or decrease GTBLHASH. </li>
	If GTBLRU is high but GTBLRS is not, increase GTBLPCT or decrease GTBLHASH. </li>
	<li>		<li>If GTBLRS is high but GTBLRU is low, decrease GTBLPCT.</li>
	If GTBLRS is high but GTBLRU is low, decrease GTBLPCT.</li>
	</ul>		</ul>
	<p>For a discussion of the performance improvement possible handling global string variables using ~~GTBLHASH see the~~ <var>~~Model 204 User Language Manual.~~</var></p>		<p>
			For a discussion of the performance improvement possible handling global string variables using <var>GTBLHASH</var>, see [[Global features#Global string variables\|Global string variables]].</p>

	[[Category:User parameters]]		[[Category:User parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-08-27T16:28:38Z

Automatically generated page update

← Older revision		Revision as of 16:28, 27 August 2013
Line 1:		Line 1:
			{{Template:GTBLHASH parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>

DmeWiccan: Automatically generated page update

2013-04-23T02:06:01Z

Automatically generated page update

← Older revision		Revision as of 02:06, 23 April 2013
Line 42:		Line 42:
	</ul>		</ul>
	<p>For a discussion of the performance improvement possible handling global string variables using GTBLHASH see the <var>Model 204 User Language Manual.</var></p>		<p>For a discussion of the performance improvement possible handling global string variables using GTBLHASH see the <var>Model 204 User Language Manual.</var></p>
	[[Category:User ~~Parameters~~]]		[[Category:User parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Alex: Automatically generated page update

2013-02-28T00:55:51Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>User
<dt>Where set
<dd>By any user
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V6.1</var> or earlier
</dl>
==Description==
The number of hash buckets allocated in GTBL to hold global string variable names. The benefit of using GTBLHASH is that the scan time and CPU time to find and update global string variables is reduced, typically, by a factor of GTBLHASH.
When a global string variable is set or retrieved, the name of the global is hashed into one of the GTBLHASH buckets. Once the bucket is determined, the scanning and updating works as it did prior to Version 5.1, except there is less data to move when a value is deleted or its size changes.
By default, when you place a global string variable in GTBL, it is stored in order-of-entry. If you set GTBLHASH to a nonzero value the data is placed in GTBL in the order determined by the hash value of the global string variable name.
Rocket Software recommends that you set the number of buckets to a prime number, which is not greater than the expected maximum number of global variables divided by four. You can find your optimal value through experimentation; Rocket Software recommends that you start with a relatively small number such as five or seven.
Resetting the GTBLHASH parameter clears the global table.
====Calculating GTBL space requirements====
When hashed GTBL is being used, GTBL requires an extra 8 bytes for every hash bucket, which means that you should probably increase LGTBL by at least 8 times the value of GTBLHASH. Since hashing does not distribute hash values exactly evenly between buckets, you should probably increase the size of GTBL by somewhat more than this for a little extra space in each bucket. 
Rocket Software recommends that you increase LGTBL by GTBLHASH * (8 + av_len * 3) where av_len is the average expected length of the global string variable names, plus their values. So, if GTBLHASH is being set to seven and the average expected length of globals and their values is 20, LGTBL would be increased as follows: 
7 * (8 + 20 * 3) = 476.

Rearranging GTBL and tracking the rearrangements 
The benefit of using GTBLHASH is that the CPU time to find and update globals is typically reduced by a factor of GTBLHASH. 
 If there is no room to fit a global variable into its target bucket or there is no room to add a global string variable to GTBL, the hashed GTBL feature rearranges GTBL to make room. These rearrangements can be CPU intensive and could become a performance problem, if performed frequently. Because of this, the following statistics are available as system statistics, user statistics and since-last statistics to keep track of GTBL rearrangements required for the hashed GTBL feature:

<table>
<tr><th>Statistic </th><th>Tracking</th></tr>
<tr><th><var>GTBLRU </var></th><td>Number of GTBL rearrangements required to add a string variable global.</td></tr>
<tr><th><var>GTBLRS </var></th><td>Number of GTBL rearrangements required to add a global object. </td></tr>
</table>
After reviewing the GTBLRU and GTBLRS statistics, you can consider taking the following actions: 
<ul>
<li>
If both of these values are high, increase the size of GTBL by increasing LGTBL. </li>
<li>
If GTBLRU is high but GTBLRS is not, increase GTBLPCT or decrease GTBLHASH. </li>
<li>
If GTBLRS is high but GTBLRU is low, decrease GTBLPCT.</li>
</ul>
For a discussion of the performance improvement possible handling global string variables using GTBLHASH see the <var>Model 204 User Language Manual.</var>
[[Category:User Parameters]]
[[Category:Parameters]]