Our sqlite db is about 200MB, its plenty fast EXCEPT when it has to do
a large sync, then we'll likely get timeouts from concurrent requests
trying to lock the database. Generally, when we tag the trunk, or
make a branch. Other then that its all good. <br>
<br>
If I'm correct the current development code is much more efficient in
those regards (recording copies), so that problem is likely to go away
in the next release?<br>
<br>
--paul<br>
<br><br><div><span class="gmail_quote">On 6/20/05, <b class="gmail_sendername">Lewis Gardner (TYCO)</b> <<a href="mailto:lgardner@tycoint.com">lgardner@tycoint.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Does the size of the (SQLLite) database depend on the size of the subversion<br>repository? I have created a new Trac project pointing it to an existing,<br>fairly large subversion repository and a) the indexing operation took 10
<br>minutes and b) the resulting database was 78MB. This also causes the web<br>interface to be so slow that I regularly get timeouts.<br><br>Have I stumbled over a Trac limitation or did I do something very wrong?<br><br>
Thanks,<br>Lewis<br><br><br>_______________________________________________<br>Trac mailing list<br><a href="mailto:Trac@lists.edgewall.com">Trac@lists.edgewall.com</a><br><a href="http://lists.edgewall.com/mailman/listinfo/trac">
http://lists.edgewall.com/mailman/listinfo/trac</a><br></blockquote></div><br>