1<?xml version="1.0" encoding="UTF-8" standalone="no"?> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 3<html xmlns="http://www.w3.org/1999/xhtml"> 4 <head> 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 6 <title>Performance Tuning</title> 7 <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> 8 <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> 9 <link rel="start" href="index.html" title="Getting Started with Berkeley DB Transaction Processing" /> 10 <link rel="up" href="introduction.html" title="Chapter 1. Introduction" /> 11 <link rel="prev" href="recovery-intro.html" title="Recoverability" /> 12 <link rel="next" href="enabletxn.html" title="Chapter 2. Enabling Transactions" /> 13 </head> 14 <body> 15 <div class="navheader"> 16 <table width="100%" summary="Navigation header"> 17 <tr> 18 <th colspan="3" align="center">Performance Tuning</th> 19 </tr> 20 <tr> 21 <td width="20%" align="left"><a accesskey="p" href="recovery-intro.html">Prev</a> </td> 22 <th width="60%" align="center">Chapter 1. Introduction</th> 23 <td width="20%" align="right"> <a accesskey="n" href="enabletxn.html">Next</a></td> 24 </tr> 25 </table> 26 <hr /> 27 </div> 28 <div class="sect1" lang="en" xml:lang="en"> 29 <div class="titlepage"> 30 <div> 31 <div> 32 <h2 class="title" style="clear: both"><a id="perftune-intro"></a>Performance Tuning</h2> 33 </div> 34 </div> 35 </div> 36 <p> 37 From a performance perspective, the use of transactions is not free. 38 Depending on how you configure them, transaction commits 39 usually require your application to perform disk I/O that a non-transactional 40 application does not perform. Also, for multi-threaded 41 <span>and 42 multi-process</span> applications, the use of transactions can 43 result in increased lock contention due to extra locking 44 requirements driven by transactional isolation guarantees. 45 </p> 46 <p> 47 There is therefore a performance tuning component to transactional applications 48 that is not applicable for non-transactional applications (although 49 some tuning considerations do exist whether or not your application uses 50 transactions). Where appropriate, these tuning considerations are 51 introduced in the following chapters. 52 53 <span> 54 However, for a more complete description of them, see the 55 <a class="ulink" href="http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/tune.html" target="_top"> 56 Transaction tuning 57 </a> 58 and 59 <a class="ulink" href="http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/throughput.html" target="_top"> 60 Transaction throughput 61 </a> 62 sections of the <em class="citetitle">Berkeley DB Programmer's Reference Guide</em>. 63 </span> 64 65 </p> 66 </div> 67 <div class="navfooter"> 68 <hr /> 69 <table width="100%" summary="Navigation footer"> 70 <tr> 71 <td width="40%" align="left"><a accesskey="p" href="recovery-intro.html">Prev</a> </td> 72 <td width="20%" align="center"> 73 <a accesskey="u" href="introduction.html">Up</a> 74 </td> 75 <td width="40%" align="right"> <a accesskey="n" href="enabletxn.html">Next</a></td> 76 </tr> 77 <tr> 78 <td width="40%" align="left" valign="top">Recoverability </td> 79 <td width="20%" align="center"> 80 <a accesskey="h" href="index.html">Home</a> 81 </td> 82 <td width="40%" align="right" valign="top"> Chapter 2. Enabling Transactions</td> 83 </tr> 84 </table> 85 </div> 86 </body> 87</html> 88