71 lines
4.6 KiB
HTML
71 lines
4.6 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
<!DOCTYPE html
|
||
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
<html lang="en-us" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow" />
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<meta name="DC.Type" content="reference" />
|
||
|
<meta name="DC.Title" content="Fine-tune record-blocking" />
|
||
|
<meta name="abstract" content="Record-blocking is a technique that significantly reduces the number of network flows." />
|
||
|
<meta name="description" content="Record-blocking is a technique that significantly reduces the number of network flows." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaikodbcperfarch.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaikconnstrkeywordsperfprop.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="odbcfinetunercdblock" />
|
||
|
<meta name="DC.Language" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
<title>Fine-tune record-blocking</title>
|
||
|
</head>
|
||
|
<body id="odbcfinetunercdblock"><a name="odbcfinetunercdblock"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Fine-tune record-blocking</h1>
|
||
|
<div><p><strong>Record-blocking</strong> is a technique that significantly reduces
|
||
|
the number of network flows. </p>
|
||
|
<div class="section"><p>It does this by returning a <em>block</em> of rows from the server
|
||
|
on the first FETCH request for a cursor. Subsequent FETCH requests are retrieved
|
||
|
from the local block of rows, rather then going to the server each time. This
|
||
|
technique dramatically increases performance when it is properly used. The
|
||
|
default settings should be sufficient for most situations.</p>
|
||
|
</div>
|
||
|
<div class="section"><p>A change to one of the record-blocking parameters can make a significant
|
||
|
difference when the performance of your environment is approaching the exponential
|
||
|
threshold that is illustrated in <a href="rzaikintrocsperf.htm#introcsperf">Introduction to client/server performance</a>.
|
||
|
For example, assume that an environment has <em>n</em> decision-support clients
|
||
|
doing some amount of work with large queries, typically returning 1 MB of
|
||
|
data. </p>
|
||
|
</div>
|
||
|
<div class="section"><p>At the opposite extreme is a scenario where users consistently
|
||
|
ask for large amounts of data, but typically never examine more than a few
|
||
|
rows. The overhead of returning 32KB of rows when only a few are needed could
|
||
|
degrade performance. Setting the <em>BLOCKSIZE</em> or <em>BlockSizeKB</em> connection
|
||
|
string keyword to a lower value, setting the <em>BLOCKFETCH</em> connection
|
||
|
string keyword to 0 (Use ODBC blocking) or disabling record blocking altogether,
|
||
|
might actually increase performance.</p>
|
||
|
</div>
|
||
|
<div class="section"><p>It is important to note that, as always in client/server, performance
|
||
|
results may vary. You might make changes to these parameters and not realize
|
||
|
any difference. This may indicate that your performance bottleneck is not
|
||
|
the client request queue at the server. This parameter gives you one more
|
||
|
tool to use when your users start objecting.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikodbcperfarch.htm" title="For the iSeries Access for Windows ODBC driver, all of the internal data flows between the client and the server are chained together, and transmit only when needed.">The performance architecture of the iSeries Access for Windows ODBC driver</a></div>
|
||
|
</div>
|
||
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
<div><a href="rzaikconnstrkeywordsperfprop.htm" title="Use these iSeries Access ODBC driver connection string keywords to change Performance properties of the ODBC connection.">Connection string keywords - Performance properties</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|