On 06/08/2011 08:37 AM, Mikhail Gusarov wrote: >> FYI Cfengine supports two other databases: Tokyo Cabinet and QDBM. >> >> If you compile from source, use --with-tokyocabinet to use that >> database instead of Berkeley. >> It does locking and is "probably faster" (would be cool with a >> comparison, hint hint) - at least according to stats on its home page. >> This might be part of the solution we choose going forward due to the >> corruption issues (together with some weird memory errors from time to >> time) with Berkeley DB. > > Even then, some additional integrity checking will be needed, as TC is > as prone to hang up on corrupted DB as Berkeley DB. I know SQLite is > much better in this aspect (being ACID), but it comes with additional price.
Out of curiosity I have implemented storing Cfengine data in SQLite 3 (just pushed to trunk, r2380-r2382). It is really slow due to lot of commits during cf-agent run, but might be funny to work with (or optimize other code). We could probably use it to find database usage bottlenecks, they become much more evident with SQLite backend :) _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
