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.62.4" /> 9 <link rel="home" 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="previous" 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></div> 36 </div> 37 <p> 38 From a performance perspective, the use of transactions is not free. 39 Depending on how you configure them, transaction commits 40 usually require your application to perform disk I/O that a non-transactional 41 application does not perform. Also, for multi-threaded 42 <span>and 43 multi-process</span> applications, the use of transactions can 44 result in increased lock contention due to extra locking 45 requirements driven by transactional isolation guarantees. 46 </p> 47 <p> 48 There is therefore a performance tuning component to transactional applications 49 that is not applicable for non-transactional applications (although 50 some tuning considerations do exist whether or not your application uses 51 transactions). Where appropriate, these tuning considerations are 52 introduced in the following chapters. 53 54 <span> 55 However, for a more complete description of them, see the 56 <a href="http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/tune.html" target="_top"> 57 Transaction tuning 58 </a> 59 and 60 <a href="http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/throughput.html" target="_top"> 61 Transaction throughput 62 </a> 63 sections of the <i class="citetitle">Berkeley DB Programmer's Reference Guide</i>. 64 </span> 65 66 </p> 67 </div> 68 <div class="navfooter"> 69 <hr /> 70 <table width="100%" summary="Navigation footer"> 71 <tr> 72 <td width="40%" align="left"><a accesskey="p" href="recovery-intro.html">Prev</a>��</td> 73 <td width="20%" align="center"> 74 <a accesskey="u" href="introduction.html">Up</a> 75 </td> 76 <td width="40%" align="right">��<a accesskey="n" href="enabletxn.html">Next</a></td> 77 </tr> 78 <tr> 79 <td width="40%" align="left" valign="top">Recoverability��</td> 80 <td width="20%" align="center"> 81 <a accesskey="h" href="index.html">Home</a> 82 </td> 83 <td width="40%" align="right" valign="top">��Chapter��2.��Enabling Transactions</td> 84 </tr> 85 </table> 86 </div> 87 </body> 88</html> 89