We believe we've resolved at least some of the problems we were seeing
with the skiplist backend. The performance problem may just have been
due to memory overcommitment on our production server (we increased
the memory).
We've resolved the looping problem; it was a slight problem with one
proce
We rolled out the skiplist backend on Saturday and it could hae gone a
little better. For some reason, it seems that the performance of
fdatasync() under Solaris 2.7 is terrible under high load conditions or
maybe we're just assuming the operating system is smarter than it actually
is (or mayb
Rob Siemborski wrote:
> If it helps, we're currently planning on deploying skiplist to production
> for atleast the mailboxes database this weekend.
>
Sweet. We're dying to roll this out too, but are nervous about the lack of
production experience.
Could you post back after a couple of days, even
On Fri, 22 Feb 2002, Amos Gouaux wrote:
> Or grab Cyrus from CVS. The SMakefile shell script will do this for
> you. If you grab it from CVS, looks like you can try using seen db
> as skiplist as well.
Yes, skiplist should be able to be used for any of the databases that
cyrus maintains. We'v
> On Fri, 22 Feb 2002 13:32:32 +0100,
> Simon Matter <[EMAIL PROTECTED]> (sm) writes:
sm> How do I compile and use the new skiplist backend? I want to try it but
sm> I don't know how.
Try:
LOCALDEFS="-DCONFIG_DB_MBOX=\"(&cyrusdb_skiplist)\""; export LOCALDEFS
(adapt accordingly to the
How do I compile and use the new skiplist backend? I want to try it but
I don't know how.
Simon
