<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<link href="chrome://translator/skin/floatingPanel.css"
type="text/css" rel="stylesheet">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Lars,<br>
<br>
I am glad to hear that the next version will have a configurable
timeout.<br>
<br>
My current experience with many clients working against a central
server with a large number of <br>
changes to sync show that the timeout alone was not enough. The
timeouts were still being hit at the <br>
1 second retries and still unable to capture a lock before the
extended timeouts expired. By adding the <br>
usleep to increase then number of attempts per second and tuning
both variables allowed most of the <br>
lock contention went away.<br>
<br>
I think one of the issues is that with the larger number of clients
working the db file <br>
we are seeing the higher number of connection attempts to the db
file and with just<br>
the timeout you will continue to see the lock contention because
checking once a <br>
second isn't aggressive enough to actually get a lock when
competition is high.<br>
<br>
I think it is important to have those variables available and
configurable in the next version as every <br>
environment is unique and depending on how busy the networks,
servers, and other architecture.<br>
Having the ability to tweak these two key variables may allow for a
more useful experience in the larger <br>
or more intensively utilized setups.<br>
<br>
Catch you later,<br>
<br>
Chuck Handshy<br>
H2Consulting, LLC.<br>
<br>
<br>
<div style="bottom: auto; left: 390px; right: auto; top: 386px;
display: none;" class="translator-theme-default"
id="translator-floating-panel">
<div title="Click to translate"
id="translator-floating-panel-button"></div>
</div>
</body>
</html>