<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Batch Mode</title>
<link rel="stylesheet" type="text/css" href="../../style.css">
</head>
<body>
<div class="CommonContent">
<div class="CommonContentArea">
<h1>Batch Mode</h1><p>Client-server batch messaging mode was introduced in db4o
version 6.1. This mode allows to increase the performance by reducing
client/server communication.</p>
<span name="cs_wiki_filter" csw_filters="cs"><p>c#: </p>
<p><code>container.Ext().Configure().ClientServer().BatchMessages(true);</code></p>
</span>
<span name="cs_wiki_filter" csw_filters="vb"><p>VB: </p>
<p><code>container.Ext().Configure().ClientServer().BatchMessages(true);</code></p>
</span>
<p>How it works? Db4o client communicates with the server by
means of messaging. In the default mode (<code>batchMessages(false)</code>)
db4o client sends a message with an instruction to the server and waits for the
response. This might be quite inefficient when there are many small messages to
be sent (like bulk inserts, updates, deletes): network communication becomes a
bottleneck. Batch messaging mode solves this problem by caching the client
messages on the client before sending them to the server. </p>
<p>The advantages of the batch messaging mode are:</p>
<ul><li>reduced network load;</li><li>increased performance for bulk operations.</li></ul>
<p>The downside is:</p>
<ul><li>increased memory consumption on both the client and the server.</li></ul> <div class="childTopicList">More Reading:<ul>
<li><p><a href="batch_mode/controlling_memory_consumption.html" class="wikiLink">Controlling Memory Consumption</a></p></li>
<li><p><a href="batch_mode/batch_messaging_example.html" class="wikiLink">Batch Messaging Example</a></p></li>
</ul></div>
</div>
</div>
<div id="footer">
This revision (5) was last Modified 2007-03-13T19:42:31 by Tetyana.
</div>
</body>
</html>
